From: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: x86 incomplete/WIP software single-step implementation (Re: [PATCH] Do not respawn signals, take 2.)
Date: Wed, 04 Jul 2012 15:35:00 -0000 [thread overview]
Message-ID: <4FF46296.9000706@redhat.com> (raw)
In-Reply-To: <4FEC9998.2040001@redhat.com>
On 06/28/2012 06:51 PM, Pedro Alves wrote:
> While I was waiting to get access to some Red Hat ARM machines,
> I started cooking up a software single-step implementation
> for x86, for easier-testing purposes. I though perhaps who knows
> it might also prove useful in the future for something else, e.g.,
> block-step fallback support.
>
> I got ARM access before I finished it, so it's largely incomplete (see
> commit log), though it passes many tests. It's here in case it interests
> someone:
>
> https://github.com/palves/gdb/tree/x86_software_single_step
FYI, this is mostly complete and useable now. A few displaced-stepping
regressions remain, and reverse debugging breaks (but ISTR that was a generic
software single-step issue? If so, this should help debug it). I've also
tested this with a hack that forces single-step for everything (including "continue")
(there's a branch for that, see my github's wiki). This should make
developing/testing all-stop-on-top-of-non-stop on software single-step
archs a bit easier (for me).
--
Pedro Alves
next prev parent reply other threads:[~2012-07-04 15:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 14:55 [PATCH] Do not respawn signals, take 2 Pedro Alves
2012-06-22 15:05 ` Jan Kratochvil
2012-06-22 15:12 ` Pedro Alves
2012-06-22 16:07 ` Jan Kratochvil
2012-06-28 17:51 ` x86 incomplete/WIP software single-step implementation (Re: [PATCH] Do not respawn signals, take 2.) Pedro Alves
2012-07-04 15:35 ` Pedro Alves [this message]
2012-07-04 19:45 ` Mark Kettenis
2012-06-22 19:18 ` [PATCH] Do not respawn signals, take 2 Jan Kratochvil
2012-06-28 17:28 ` Pedro Alves
2012-06-28 17:32 ` Jan Kratochvil
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=4FF46296.9000706@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@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