This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Support targets that know how to step over breakpoints
- From: Pedro Alves <palves at redhat dot com>
- To: lgustavo at codesourcery dot com
- Cc: gdb-patches at sourceware dot org
- Date: Tue, 27 Nov 2012 16:20:13 +0000
- Subject: Re: [PATCH] Support targets that know how to step over breakpoints
- References: <506D859E.9050600@codesourcery.com> <507E99BB.8050105@codesourcery.com> <508FB2B6.6040006@codesourcery.com> <50B4DA35.3010206@codesourcery.com>
On 11/27/2012 03:20 PM, Luis Machado wrote:
> Meanwhile i've updated this patch for the latest cvs head.
>
> I'm wondering if the patch is too ugly for someone to take a look at it or if it is too odd a feature to add. I suppose not.
>
> Hopefully i can get some traction with this new refreshed and shiny version! :-)
I was hoping others could comment. :-)
Last we discussed this (probably a years ago already), I expressed my
concern with upstreaming this as is. It's that this works by sending a regular
step command to the target, and then the target steps over any breakpoint that
may be at the current PC. If GDB is wanting to move past a breakpoint, this still
needs to do:
-> vCont;s
<- T05 (step finished)
<- vCont;c
An alternative would be to get rid of that T05, by defining new commands that
tell the target to step-over-breakpoint, or continue-over-breakpoint (and signal
variants). E.g., sbc to mean step-break-continue:
-> vCont;spc
That'd move past the breakpoint without causing a stop immediately.
Guess I need to convince myself the current design is good enough. Comments?
--
Pedro Alves