From: khan@xraylith.wisc.edu (Mumit Khan)
To: help-gcc@gnu.org
Subject: Re: Forcing thrown exceptions to core dump without stack unwinding?
Date: Fri, 31 Dec 1999 22:24:00 -0000 [thread overview]
Message-ID: <82aecc$cpq$1@news.doit.wisc.edu> (raw)
Message-ID: <19991231222400.VQhcW4faKvJ2MNcGFnvflvoDZCj0iOhGIXSU0B7cM7Q@z> (raw)
In-Reply-To: <829qlj$80e@spool.cs.wisc.edu>
In article < 829qlj$80e@spool.cs.wisc.edu >, Andy Glew <glew@cs.wisc.edu> wrote:
>I'm using GCC 2.95.
>Q: is there a way of forcing thrown exceptions to core dump
>at the site of the exception - so that I can get a useful core dump
>I can look at in a debugger?
This is IMO a real issue with current EH implementation in GCC. One way
to fix is to implement a dual pass: (1) "virtually" unwind the stack
looking for a handler, and (2) if found, call the handler; if not, call
terminate in the context of the current frame. Essentially, you get a
C-like assertion if you don't have a handler for that exception.
>My program may run for many days before the core dump (or not).
>It is impractical to run them in a debugger set to break at the first
>exception. Since the exceptions seem to be arising in library functions
>I have not written, it is impractical to change the code to optionally
>not throw.
I know the feeling. I have numercial codes that runs from days to weeks
at a time, and it's very frustrating when you can't pinpoint where things
went wrong. You can get around *some of it* by inserting "catch all"
blocks around library codes, but it's still messy.
>Please email to glew@cs.wisc.edu
And posted of course.
Regards,
Mumit
next prev parent reply other threads:[~1999-12-31 22:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-03 17:33 Andy Glew
1999-12-03 23:13 ` Mumit Khan [this message]
1999-12-31 22:24 ` Mumit Khan
1999-12-31 22:24 ` Andy Glew
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='82aecc$cpq$1@news.doit.wisc.edu' \
--to=khan@xraylith.wisc.edu \
--cc=help-gcc@gnu.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).