From: Doug Evans <dje@google.com>
To: gdb@sourceware.org
Subject: Re: i386 int3 handling, running vs stepping
Date: Mon, 02 Feb 2009 20:03:00 -0000 [thread overview]
Message-ID: <e394668d0902021203u47b5a22fg9be1b3e987551154@mail.gmail.com> (raw)
In-Reply-To: <20090202042459.GA10080@caradoc.them.org>
On Sun, Feb 1, 2009 at 8:24 PM, Daniel Jacobowitz <drow@false.org> wrote:
> On Sun, Feb 01, 2009 at 03:38:04PM -0800, Doug Evans wrote:
>> I haven't looked into siginfo, but can gdb look at the insn? [akin to
>> displaced stepping handling]
>
> I suppose, but I don't really see a point.
Apologies, it's not clear what point you're referring to.
I guess the issue is whether int3's in programs are supported by gdb,
and by supported I mean users can rely on gdb flagging a SIGTRAP when
they're executed. As you say, there are people who take advantage of
this for hardwired breakpoints.
There are various situations where gdb itself will singlestep code
(e.g., "step", "next", s/w watchpoints). Can users expect to see the
SIGTRAP in these situations (and all others)? And if the program is
being run by a script, can the script expect to see the SIGTRAP in all
cases?
next prev parent reply other threads:[~2009-02-02 20:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-01 23:18 Doug Evans
2009-02-01 23:33 ` Daniel Jacobowitz
2009-02-01 23:38 ` Doug Evans
2009-02-02 4:25 ` Daniel Jacobowitz
2009-02-02 20:03 ` Doug Evans [this message]
2009-02-02 21:49 ` Daniel Jacobowitz
2009-02-03 1:26 ` Doug Evans
2009-02-03 4:08 ` Daniel Jacobowitz
2009-02-03 9:22 ` Mark Kettenis
2009-02-02 0:52 ` Doug Evans
2009-02-02 6:08 ` Robert Dewar
2009-02-02 6:19 ` teawater
2009-02-03 9:21 ` Mark Kettenis
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=e394668d0902021203u47b5a22fg9be1b3e987551154@mail.gmail.com \
--to=dje@google.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