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

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: sen_ml@xxxxxxxxxxx
Date: Thu, 17 Dec 1998 10:38:36 +0900
At around Wed, 16 Dec 1998 11:22:15 -0800 (PST),
 guy@xxxxxxxxxx (Guy Harris) may have mentioned:

> > 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...).

the signal which appeared was numbered 6 -- which i think is ABRT.