From: Phil Muldoon <pmuldoon@redhat.com>
To: gdb@sourceware.org
Subject: unwindonsignal variable question
Date: Tue, 16 Sep 2008 15:58:00 -0000 [thread overview]
Message-ID: <48CFD764.2050405@redhat.com> (raw)
Setting this to "on" fixes the most problematic aspects of gnats pr
2495. (This is where an exception is raised in a C++ function executed
by inferior function call, and no in-frame exception handler results in
a sigabrt being delivered to the inferior).
As this is a very useful flag, and it only seems to apply in inferior
function calls, I am curious why it appears to default as "off",
requiring the user to perform:
set unwindonsignal on
(I'm not advocating changing it, just curious if there is a particular
reason for it to be this way). And also, if there would be known
side-effects to having it to default as on.
Regards
Phil
next reply other threads:[~2008-09-16 15:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-16 15:58 Phil Muldoon [this message]
2008-09-16 16:12 ` Daniel Jacobowitz
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=48CFD764.2050405@redhat.com \
--to=pmuldoon@redhat.com \
--cc=gdb@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