From: Roland McGrath <roland@redhat.com>
To: Andrew Cagney <cagney@redhat.com>
Cc: frysk@sourceware.org
Subject: Re: elfutls using assert
Date: Mon, 09 Jul 2007 23:08:00 -0000 [thread overview]
Message-ID: <20070709230811.DCB0C4D0585@magilla.localdomain> (raw)
In-Reply-To: Andrew Cagney's message of Monday, 9 July 2007 08:38:22 -0400 <46922C3E.9040301@redhat.com>
No, there is no way not to call abort. It is used for situations that are
pathological in the same way as a clobbered pointer that might lead to a
crash. If you want to improve recovery from such bugs, you might as well
catch all unexpected fatal signals and diagnose gracefully there (maybe if
things aren't too bad you can throw an exception from the signal handler
and never consult the clobbered data structures while reporting and exiting).
next prev parent reply other threads:[~2007-07-09 23:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 12:38 Andrew Cagney
2007-07-09 23:08 ` Roland McGrath [this message]
2007-07-10 15:34 ` Andrew Cagney
2007-07-10 18:47 ` Roland McGrath
2007-07-12 15:10 ` 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=20070709230811.DCB0C4D0585@magilla.localdomain \
--to=roland@redhat.com \
--cc=cagney@redhat.com \
--cc=frysk@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).