From: Andreas Schwab <schwab@issan.informatik.uni-dortmund.de>
To: Arun Sharma <asharma@netscape.com>
Cc: egcs@cygnus.com
Subject: Re: EGCS vs MSVC - exception handling
Date: Wed, 14 Jan 1998 02:14:00 -0000 [thread overview]
Message-ID: <vyz67nnz7u0.fsf@issan.informatik.uni-dortmund.de> (raw)
In-Reply-To: <sn090sk7rg3.fsf@zugzwang.mcom.com>
Arun Sharma <asharma@netscape.com> writes:
|> Jeffrey A Law <law@cygnus.com> writes:
|>> That requires quite a bit more work. You might start with adding
|>> -fasynchronous-exceptions to the command line (or something close to that)
|>> which instructs flow to create an edge from every insn to its EH handler
|>> (since just about any insn could trap into a signal handler).
|> Why would that be necessary ? Inside the signal handler, I know
|> precisely which instruction generated the trap by looking into the
|> sigcontext. All I need to do is to be able to unwind the stack and
|> look for the right exception handler to call.
The sigcontext is as unportable as you can get.
--
Andreas Schwab "And now for something
schwab@issan.informatik.uni-dortmund.de completely different"
schwab@gnu.org
next prev parent reply other threads:[~1998-01-14 2:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <34bbf4a0.7558458@nntp.demos.su>
[not found] ` <u1zyekkhq.fsf@finobj.com>
[not found] ` <34bf0215.11003532@nntp.demos.su>
[not found] ` <uzpl1kbmy.fsf@finobj.com>
1998-01-12 10:18 ` Arun Sharma
1998-01-12 17:07 ` Jeffrey A Law
1998-01-13 4:31 ` Arun Sharma
1998-01-14 2:14 ` Andreas Schwab [this message]
1998-01-14 4:17 ` Jeffrey A Law
1998-01-15 16:30 ` Richard Henderson
1998-01-15 16:13 Mike Stump
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=vyz67nnz7u0.fsf@issan.informatik.uni-dortmund.de \
--to=schwab@issan.informatik.uni-dortmund.de \
--cc=asharma@netscape.com \
--cc=egcs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).