From: teawater <teawater@gmail.com>
To: "Pedro Alves" <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Target can step over breakpoints itself
Date: Tue, 28 Oct 2008 05:59:00 -0000 [thread overview]
Message-ID: <daef60380810272020m6e8b272eufa70ec6a52090637@mail.gmail.com> (raw)
In-Reply-To: <200810271419.00304.pedro@codesourcery.com>
This patch is cool!
I make a simulator can step over breakpoint with itself in before. I
think a lot of simulator can do it too. Cause they can control
breakpoint with itself.
On Mon, Oct 27, 2008 at 22:19, Pedro Alves <pedro@codesourcery.com> wrote:
> When adding non-stop debugging support to a target/arch, one of the
> most important aspects we need to take care of, is to have a means
> to step over breakpoints without removing them from the inferior,
> otherwise, other running threads may miss them. We've added a mechanism
> to GDB that does out-of-line single-stepping (displaced stepping), which
> we use on linux x86 and ppc. The smarts to do this are all on the GDB side.
>
> DICOS debug API can take care of magically stepping over software
> breakpoints transparently, which means that we don't have to resort to
> do displaced stepping on the GDB side.
>
> The attached patch adds a new "StepOverBreakpoints" feature to the
> remote protocol to the remote stub can tell GDB that the debug api has
> that feature, and exposes that knowledge to the rest of GDB by
> adding a new target_ops method (target_can_step_over_breakpoints),
> and teaching infrun.c to it doesn't need to do the traditional hold-and-step
> dance (remove breakpoints, single-step, insert breakpoints) from the
> inferior(s), if the target reports support for stepping over them
> itself.
>
> Any objections/thoughts on this?
>
> --
> Pedro Alves
>
next prev parent reply other threads:[~2008-10-28 3:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 14:19 Pedro Alves
2008-10-28 5:59 ` teawater [this message]
2008-10-28 14:20 ` Daniel Jacobowitz
2008-11-03 15:45 ` Pedro Alves
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=daef60380810272020m6e8b272eufa70ec6a52090637@mail.gmail.com \
--to=teawater@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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