Re: Segfault in current bzr

[grischka]

> At least that can be avoided without letting go of optimization:
> cf. C-h C-d
>
> ** When you are trying to analyze failed assertions, it will be
> essential to compile Emacs either completely without optimizations or
> at least (when using GCC) with the -fno-crossjumping option.  Failure
> to do so may make the compiler recycle the same abort call for all
> assertions in a given function, rendering the stack backtrace useless
> for identifying the specific failed assertion.

Typically emacs:  They're rather able to give people a lecture about
gcc options than to add a simple one-line wrapper for abort to print
the file:linenumber.

--- grischka