[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: The emacs_backtrace "feature"
From: |
Eli Zaretskii |
Subject: |
Re: The emacs_backtrace "feature" |
Date: |
Sun, 30 Sep 2012 09:14:49 +0200 |
> From: Stefan Monnier <address@hidden>
> Cc: Juri Linkov <address@hidden>, address@hidden, address@hidden
> Date: Sat, 29 Sep 2012 21:48:39 -0400
>
> 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).
Sorry, I don't follow: the eassert macro includes the file name and
the line number in the message it prints, together with the condition
that was violated.
- 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, 2012/09/29
Re: The emacs_backtrace "feature",
Eli Zaretskii <=
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