batch-bytecomp backtrace?

[Miles Bader]

Hi Stefan, I notice this change:

   2004-04-14  Stefan Monnier  <address@hidden>

           * emacs-lisp/bytecomp.el (batch-byte-compile-file):
           Give a backtrace if requested.

which looks very handy, but I can't figure out how to make it work.

I'm having the following error when bootstrapping emacs:

   Compiling /home/m/miles/src/emacs/lisp/./eshell/esh-module.el
   Loading ange-ftp (source)...
   Loading vc-arch (source)...

   In toplevel form:
   ../../../src/emacs/lisp/eshell/esh-module.el:29:13:Error: Lisp nesting 
exceeds max-lisp-eval-depth
   make[1]: *** [compile] Error 1
   make[1]: Leaving directory `/home/m/miles/build/emacs/lisp'
   make: *** [bootstrap] Error 2

So I thought it would be perfect time to see a backtrace (compiling
interactively succeeds!); I tried:

   src/bootstrap-emacs -batch -f toggle-debug-on-error -f batch-byte-compile 
~/src/emacs/lisp/eshell/esh-module.el

   src/bootstrap-emacs -batch --eval '(setq debug-on-error t)' -f 
batch-byte-compile ~/src/emacs/lisp/eshell/esh-module.el

   src/bootstrap-emacs -batch --eval '(let ((debug-on-error t)) 
(batch-byte-compile "~/src/emacs/lisp/eshell/esh-module.el"))'

but all simply printed an error message and quit like a normal
(debug-on-error = nil) batch byte-compile.

So what magic is necessary to get a backtrace??

Thanks,

-Miles

p.s. The option `-e' should really do `--eval' ...!
-- 
`Cars give people wonderful freedom and increase their opportunities.
 But they also destroy the environment, to an extent so drastic that
 they kill all social life' (from _A Pattern Language_)