From: Daniel Jacobowitz <drow@false.org>
To: Michael Snyder <msnyder@vmware.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: Do not call write_pc for "signal SIGINT"
Date: Thu, 28 Aug 2008 22:33:00 -0000 [thread overview]
Message-ID: <20080828223232.GA6407@caradoc.them.org> (raw)
In-Reply-To: <48B6EFBD.2090203@vmware.com>
On Thu, Aug 28, 2008 at 11:34:37AM -0700, Michael Snyder wrote:
> More than a testcase. This isn't very well explained.
> You didn't reference the PR in your original post, and
It was in the ChangeLog entry, sorry.
> I'm still not sure how we're getting from SIGINT to
> signal 0...
We aren't. The comment that I'm deleting is talking about the user
typing "signal 0", which worked correctly; I'm making "signal SIGINT"
treat the PC the same way. All the complexity is in incorrect bits
I'm deleting :-) Afterwards it's like every other call to proceed in
the file.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-08-28 22:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 15:56 Daniel Jacobowitz
2008-08-28 18:13 ` Michael Snyder
2008-08-28 18:19 ` Daniel Jacobowitz
2008-08-28 18:38 ` Michael Snyder
2008-08-28 22:33 ` Daniel Jacobowitz [this message]
2008-11-18 4:18 ` Daniel Jacobowitz
2008-11-18 5:46 ` Pedro Alves
2009-01-20 15:32 ` 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=20080828223232.GA6407@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.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