This is the mail archive of the
mailing list for the GDB project.
Re: abort() to internal_error()
- To: Andrew Cagney <ac131313 at cygnus dot com>
- Subject: Re: abort() to internal_error()
- From: jtc at redback dot com (J.T. Conklin)
- Date: 16 Feb 2001 12:07:54 -0800
- Cc: GDB Discussion <gdb at sources dot redhat dot com>,Kevin Buettner <kevinb at cygnus dot com>
- References: <3A8D419B.35FE24C@cygnus.com>
- Reply-To: jtc at redback dot com
>>>>> "Andrew" == Andrew Cagney <firstname.lastname@example.org> writes:
Andrew> KevinB's kindly cooked up a script that will replace all instances of:
Andrew> abort ();
Andrew> internal_error (__FILE__, __LINE__, "function calls abort ()");
Andrew> Applying and committing this script will signify the end of a very long
Andrew> campain I've been waging with GDB - to significantly reduce the
Andrew> likelhood that GDB dumps core.
This is good enough to go in as is, but I wonder if there is any way
can improve the message. IMO "function calls abort ()" is wrong, or
at best misleading, since the function no longer calls abort().
Perhaps "failed internal consistancy check" is generic enough without
Of course, these can, and I suspect will be changed to be specific to
the error condition in the fullness of time.