[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Skipping unexec via a big .elc file
From: |
Stefan Monnier |
Subject: |
Re: Skipping unexec via a big .elc file |
Date: |
Sat, 14 Jan 2017 13:11:26 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) |
>> You can set byte-compile-debug (along with debug-on-error) to get
>> a backtrace which will be more useful.
> That doesn't help when one is presented with a build log.
Not directly, no, indeed. Usually I then fire an interactive Emacs, set
the vars and call byte-compile-file to reproduce the problem in an
environment where I can investigate the backtrace comfortably.
My point was simply that this is an *evaluation* error more than an error
in the compiled code, so the poverty of the info is due to the poverty
of info we get when running Elisp code (and this is indeed somewhat
linked to the byte-compiler since the byte-compiler doesn't preserve
the source location in the bytecode it emits).
Stefan
- Re: Skipping unexec via a big .elc file, (continued)
- Re: Skipping unexec via a big .elc file, Andreas Schwab, 2017/01/14
- Re: Skipping unexec via a big .elc file, Eli Zaretskii, 2017/01/14
- Re: Skipping unexec via a big .elc file, Alan Mackenzie, 2017/01/14
- Re: Skipping unexec via a big .elc file, Andreas Schwab, 2017/01/14
- Re: Skipping unexec via a big .elc file, Eli Zaretskii, 2017/01/14
- Re: Skipping unexec via a big .elc file, Andreas Schwab, 2017/01/14
- Re: Skipping unexec via a big .elc file, Eli Zaretskii, 2017/01/14
- Re: Skipping unexec via a big .elc file, Andreas Schwab, 2017/01/14
- Re: Skipping unexec via a big .elc file, Stefan Monnier, 2017/01/14
- Re: Skipping unexec via a big .elc file, Eli Zaretskii, 2017/01/14
- Re: Skipping unexec via a big .elc file,
Stefan Monnier <=
- Re: Skipping unexec via a big .elc file, Eli Zaretskii, 2017/01/14
- Re: Skipping unexec via a big .elc file, Ken Raeburn, 2017/01/21
- Re: Skipping unexec via a big .elc file, Ken Raeburn, 2017/01/22