[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: The emacs_backtrace "feature"
From: |
Stefan Monnier |
Subject: |
Re: The emacs_backtrace "feature" |
Date: |
Sat, 29 Sep 2012 21:48:39 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.2.50 (gnu/linux) |
>> Would be better to increase the number of lines to 24 or 32
>> or any other round number.
> Instead of guessing, I'd suggest a small research: collect all the
> backtraces reported to the bug tracker, and build the historgram of
> their sizes. Then decide based on that.
> I would also suggest some heuristics, e.g. if the crash is in GC, the
> number will have to be much larger.
I really dislike the idea of writing those backtraces into a file (when
RMS mentioned it, I was shocked), but the more it goes, the more I think
it would make sense for the non-ENABLE_CHECKING builds. Tho maybe just
not showing the backtraces at all would work just as well in those cases.
I still would prefer going back to having the easserts in macros rather
than in functions (so that the assertion itself immediately gives you
the line-number, without having to go through the addr2line rigmarole).
Stefan
- Re: The emacs_backtrace "feature", (continued)
Re: The emacs_backtrace "feature", Juri Linkov, 2012/09/29
- Re: The emacs_backtrace "feature", Eli Zaretskii, 2012/09/29
- Re: The emacs_backtrace "feature", Paul Eggert, 2012/09/29
- Re: The emacs_backtrace "feature", Eli Zaretskii, 2012/09/29
- Re: The emacs_backtrace "feature", Paul Eggert, 2012/09/29
- messages-buffer-max-lines (was: The emacs_backtrace "feature"), Juri Linkov, 2012/09/30
Re: The emacs_backtrace "feature",
Stefan Monnier <=
Re: The emacs_backtrace "feature", Eli Zaretskii, 2012/09/30
Re: The emacs_backtrace "feature", Paul Eggert, 2012/09/30
Re: The emacs_backtrace "feature", Chong Yidong, 2012/09/30
Re: The emacs_backtrace "feature", Richard Stallman, 2012/09/21