Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@cygnus.com>
To: GDB Discussion <gdb@sources.redhat.com>
Subject: Re: abort() to internal_error()
Date: Fri, 16 Feb 2001 11:59:00 -0000	[thread overview]
Message-ID: <1010216195947.ZM12211@ocotillo.lan> (raw)
In-Reply-To: <ac131313@cygnus.com>

On Feb 16, 10:04am, Andrew Cagney wrote:

> KevinB's kindly cooked up a script that will replace all instances of:
> 
> 	abort ();
> 
> with
> 
> 	internal_error (__FILE__, __LINE__, "function calls abort ()");
> 
> Applying and committing this script will signify the end of a very long
> campain I've been waging with GDB - to significantly reduce the
> likelhood that GDB dumps core.
> 
> >From memory, this has been discussed several times before (and is listed
> in the TODO file).  The only problem I can think of is the message. 
> However, if you think about it:
> 
> 	(gdb) pwd
> 	internal_error: /a/b/c/d/foo.c:47: function calls abort ()
> 	....
> 
> is still infinatly better than something like
> 
> 	(gdb) pwd
> 	Program received SIGXYZZY, core dumped
> 	$
> 
> so I think is good enough,
> 
> comments?

It should be noted that if the "function calls abort ()" message is
unpalatable for some reason (e.g, lack of specificity), these can be
replaced with something more suitable over time.  In each case, the
choice of a more suitable message will likely depend upon the context,
so I think that Andrew's suggestion is a reasonable first step.  It is
certainly better than what we have now...

Kevin


  parent reply	other threads:[~2001-02-16 11:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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   ` Kevin Buettner [this message]
2001-02-16  7:09 abort() to internal_error() Andrew Cagney
2001-02-16 12:08 ` J.T. Conklin
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

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=1010216195947.ZM12211@ocotillo.lan \
    --to=kevinb@cygnus.com \
    --cc=gdb@sources.redhat.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