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

[guy@xxxxxxxxxx (Guy Harris)]

> If running out of memory is causing Ethereal to crash, perhaps we're
> allocating memory and not checking whether the memory allocator returns
> NULL - a stack trace from one of the crashes might help here (as might
> checking the code to make sure it's not doing that...).

Sigh.  "g_malloc()" appears to call "g_error()" if memory can't be
allocated, and "g_error()" ends up calling "abort()", by default.  Memo
to self: don't use "g_malloc()" without setting the error function to
something that *doesn't* return (and thus doesn't allow it to just drop
core if you've run out of swap space...).