Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: jtc@redback.com (J.T. Conklin)
To: Andrew Cagney <ac131313@cygnus.com>
Cc: GDB Discussion <gdb@sources.redhat.com>,
	Kevin Buettner <kevinb@cygnus.com>
Subject: Re: abort() to internal_error()
Date: Fri, 16 Feb 2001 12:08:00 -0000	[thread overview]
Message-ID: <5mae7m9ysl.fsf@jtc.redback.com> (raw)
In-Reply-To: <3A8D419B.35FE24C@cygnus.com>

>>>>> "Andrew" == Andrew Cagney <ac131313@cygnus.com> writes:
Andrew> KevinB's kindly cooked up a script that will replace all instances of:
Andrew>
Andrew> 	abort ();
Andrew>
Andrew> with
Andrew>
Andrew> 	internal_error (__FILE__, __LINE__, "function calls abort ()");
Andrew>
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
mentioning abort()?

Of course, these can, and I suspect will be changed to be specific to
the error condition in the fullness of time.

        --jtc

-- 
J.T. Conklin
RedBack Networks


  reply	other threads:[~2001-02-16 12:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-16  7:09 Andrew Cagney
2001-02-16 12:08 ` J.T. Conklin [this message]
2001-02-16 12:16   ` Andrew Cagney
2001-02-16 12:39     ` Kevin Buettner
2001-02-16  7:55 Michael Elizabeth Chastain
2001-02-16  8:36 ` Andrew Cagney
     [not found] <3A25AEDA.5A57A0F2@cygnus.com>
     [not found] ` <ac131313@cygnus.com>
2000-11-29 20:15   ` free() vs xfree() vs FREEIF() vs ISO-C Kevin Buettner
2001-02-16 11:59   ` abort() to internal_error() Kevin Buettner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5mae7m9ysl.fsf@jtc.redback.com \
    --to=jtc@redback.com \
    --cc=ac131313@cygnus.com \
    --cc=gdb@sources.redhat.com \
    --cc=kevinb@cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox