Stefan Monnier <monnier@iro.umontreal.ca> schrieb am Di., 31. Jan. 2017 um
15:36 Uhr:

> > Is there a way to enter the debugger when a error in bytecomp code
> > itself is encountered? Right now, all errors including compilation ones
> > are printed to the *Compile-Log* buffer, making it impossible to get
> > a backtrace for internal compiler errors.
>
> (setq byte-compiler-debug t) ?
>
>
While there, here's a patch to document this variable: