From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: Stepping off breakpoints in non-stop debugging mode
Date: Tue, 11 Dec 2007 18:44:00 -0000 [thread overview]
Message-ID: <20071211184405.GA10876@caradoc.them.org> (raw)
In-Reply-To: <m3k5nlgkcz.fsf@codesourcery.com>
On Tue, Dec 11, 2007 at 10:24:44AM -0800, Jim Blandy wrote:
> As far as PTRACE_SINGLESTEP is concerned, isn't pushfl the only
> user instruction that can observe the state of TF anyway?
I can't answer that. Maybe Paul could. The focus of the kernel code
I was referring to is instructions which modify the state of TF;
you can observe changes by telling whether you get a trap, if
your debugger's signal handling is good enough. The debugger can do
a software single step over the pushfl instruction if it cares about
accuracy enough to bother, and/or fix up the resulting stack value.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-12-11 18:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-08 9:23 Jim Blandy
2007-12-08 17:04 ` Daniel Jacobowitz
2007-12-10 23:05 ` Jim Blandy
2007-12-10 23:17 ` Daniel Jacobowitz
2007-12-11 18:24 ` Jim Blandy
2007-12-11 18:44 ` Daniel Jacobowitz [this message]
2007-12-17 3:31 ` Thiago Jung Bauermann
2007-12-17 19:41 ` Jim Blandy
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=20071211184405.GA10876@caradoc.them.org \
--to=drow@false.org \
--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