From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Cagney <ac131313@cygnus.com>
To: Michael Elizabeth Chastain <chastain@cygnus.com>
Cc: gdb@sources.redhat.com
Subject: Re: abort() to internal_error()
Date: Fri, 16 Feb 2001 08:36:00 -0000
Message-id: <3A8D55E6.AF875E4B@cygnus.com>
References: <200102161555.HAA23672@bosch.cygnus.com>
X-SW-Source: 2001-02/msg00215.html

Michael Elizabeth Chastain wrote:
> 
> > (gdb) pwd
> > internal_error: /a/b/c/d/foo.c:47: function calls abort ()
> > ....
> 
> Fine with me.

Just FYI.  The principal was debated and agreed to months (years?) ago.
The only remaining issue (and so minor to really not be anything at all)
is the message.  Even there I don't expect people to disagree -
internal_error() regardless of the message, is infinatly better than
calling abort().

For the curious, the exact message is:

/home/scratch/GDB/src/gdb/maint.c:118: gdb-internal-error: function
calls abort ()

as in:

(gdb) maint internal-error 
/home/scratch/GDB/src/gdb/maint.c:118: gdb-internal-error: internal
maintenance
An internal GDB error was detected.  This may make further
debugging unreliable.  Continue this debugging session? (y or n) y

Create a core file containing the current state of GDB? (y or n) n
(gdb) 

	enjoy,
		Andrew