Re: Post-mortem debugging and abort

[David Kastrup]

Eli Zaretskii <address@hidden> writes:

>> From: David Kastrup <address@hidden>
>> Cc: address@hidden
>> Date: Fri, 13 Jun 2008 18:48:34 +0200
>> 
>> Well, the whole difference between exit (or maybe _exit?) and abort is
>> the core dump, and that is why abort rather than exit is also called on
>> failed assertions.  So debugging is the whole point of abort and
>> declaring it in a way that precludes debugging is a bit pointless.
>
> And even if they disagree about this, GCC and glibc could have behaved
> differently under -g.

Actually, I don't agree here: if you are hunting down a compiler bug,
you don't want to have the bug disappear as soon as you ask for
debugging symbols.  Not changing the generated code just because debug
info is output is a reasonable choice in my opinion.

One might want to have an independent code generator option -fdebug
which switches off just those optimizations that are notably awful when
debugging.

Anyway, we can discuss this on this list until we are blue in the face.
Won't change a thing.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum