Wireshark · Ethereal-users: Re: [ethereal-users] compilation questions and possible bug...

[Laurent Deniel <deniel@xxxxxxxxxxx>]

Guy Harris wrote:
> 
> > The problem is that gtk catches SIGSEGV, so no core file is generated in
> > most crashes (we should ignore SIGSEGV after gtk_init in main).
> 
> Not ignore - set to default action (SIG_IGN means you get no core dump,
> SIG_DFL means you do).

Oups, just a typo.

But on Linux and some other Unices, setting SIG_IGN on SEGV also generates 
a core dump (if I remember my debugging session in resolv.c :-)
 
> > Concerning memory allocation, g_malloc displays an error message and
> > abort() if the allocation fails.
> 
> ...which I consider broken behavior; dumping core because you've run out
> of swap space is more than a bit rude.  Perhaps you can't pop up a
> dialog box, but a core dump probably doesn't provide much useful
> information (unless the problem is that the program is leaking memory or
> something).

I agree.

--
Laurent DENIEL            | E-mail: deniel@xxxxxxxxxxx
Paris, FRANCE             |         deniel@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
                          | WWW   : http://www.worldnet.fr/~deniel
    All above opinions are personal, unless stated otherwise.