[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_ba
From: |
Stefan Monnier |
Subject: |
bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_backtrace.txt' files are written |
Date: |
Tue, 20 Nov 2012 15:15:02 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) |
>> > Accessing environment variables is another problematic place. We are
>> > crashing, so the heap or the whole arena can be trashed. Who can be
>> > sure the environment variables will not point to garbled places?
>> Just to put things in perspective: this backtrace "feature" was put in
>> to replace/supplement the previous assertion failure output (because
>> with asserts now being inside inlinable functions, the line&file info
>> we get is not the one we want any more). So the environment is usually
>> still pretty sane, because assertions are usually caught fairly early.
> If the backtrace is created due to assertion violation, yes. But it
> is also invoked for all the other fatal signals.
Yes, but the only case I care about is the assertion violation.
The other cases have never generated any useful output in the past
anyway and nobody complained abut that.
Stefan
- bug#12911: 24.3.50; let users decide where (& perhaps whether)`emacs_backtrace.txt' files are written, (continued)
- bug#12911: 24.3.50; let users decide where (& perhaps whether)`emacs_backtrace.txt' files are written, Juanma Barranquero, 2012/11/21
- bug#12911: 24.3.50; let users decide where (& perhaps whether)`emacs_backtrace.txt' filesare written, Drew Adams, 2012/11/21
- bug#12911: 24.3.50; let users decide where (& perhaps whether)`emacs_backtrace.txt' filesare written, Juanma Barranquero, 2012/11/21
- bug#12911: 24.3.50; let users decide where (& perhaps whether)`emacs_backtrace.txt' filesare written, Drew Adams, 2012/11/21
- bug#12911: 24.3.50; let users decide where (& perhaps whether)`emacs_backtrace.txt' filesare written, Juanma Barranquero, 2012/11/21
- bug#12911: 24.3.50; let users decide where (& perhaps whether)`emacs_backtrace.txt' filesare written, Drew Adams, 2012/11/21
- bug#12911: 24.3.50; let users decide where (& perhaps whether)`emacs_backtrace.txt' filesare written, Juanma Barranquero, 2012/11/21
- bug#12911: 24.3.50; let users decide where (& perhaps whether)`emacs_backtrace.txt' filesare written, Drew Adams, 2012/11/21
- bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_backtrace.txt' files are written, Stefan Monnier, 2012/11/20
- bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_backtrace.txt' files are written, Eli Zaretskii, 2012/11/20
- bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_backtrace.txt' files are written,
Stefan Monnier <=
- bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_backtrace.txt' files are written, Juanma Barranquero, 2012/11/20
- bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_backtrace.txt'files are written, Drew Adams, 2012/11/20
- bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_backtrace.txt'files are written, Eli Zaretskii, 2012/11/20
- bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_backtrace.txt'files are written, Drew Adams, 2012/11/20
- bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_backtrace.txt'files are written, Eli Zaretskii, 2012/11/20
- bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_backtrace.txt'files are written, Dani Moncayo, 2012/11/20
- bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_backtrace.txt'files are written, Eli Zaretskii, 2012/11/20
- bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_backtrace.txt'files are written, Dani Moncayo, 2012/11/20
- bug#12911: 24.3.50; let users decide where (& perhaps whether) `emacs_backtrace.txt' files are written, Eli Zaretskii, 2012/11/20