From: Daniel Jacobowitz <drow@false.org>
To: Paul Koning <pkoning@equallogic.com>
Cc: inderpreetb@gmail.com, gdb@sourceware.org
Subject: Re: GDB stub question?
Date: Wed, 26 Apr 2006 14:55:00 -0000 [thread overview]
Message-ID: <20060426140821.GA20166@nevyn.them.org> (raw)
In-Reply-To: <17487.32150.716304.944358@gargle.gargle.HOWL>
On Wed, Apr 26, 2006 at 10:03:02AM -0400, Paul Koning wrote:
> >>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:
>
> >> Is there any way we could revert back to the old way (i.e) - set
> >> breakpoint at the next address - continue - remove breakpoint.
>
> Daniel> GDB has never done this to implement source single stepping,
> Daniel> so I don't know what you want. You can't predict the next
> Daniel> address that far ahead; what if the current line contains a
> Daniel> branch?
>
> Isn't there a "target side single step" optional packet -- so if the
> stub supports that then gdb can just say "stepi" rather than the more
> laborious process of setting one or two breakpoints and doing a
> continue?
It's not optional, really. GDB's configuration determines whether it
will be used or not. And he's already using it, as far as I can tell.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-04-26 14:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 7:21 Inder
[not found] ` <a1029acd0604232313t7e0bb829ia325f3e658fc34e9@mail.gmail.com>
[not found] ` <1145862112.7595.5.camel@localhost.localdomain>
[not found] ` <a1029acd0604240126g4c766d1ft3e5ecf2c69d781e@mail.gmail.com>
2006-04-24 12:23 ` Inder
[not found] ` <20060424121630.GA19787@nevyn.them.org>
2006-04-24 15:48 ` Inder
[not found] ` <20060424123222.GA20402@nevyn.them.org>
2006-04-26 14:03 ` Inder
[not found] ` <20060426123642.GA18007@nevyn.them.org>
2006-04-26 14:08 ` Paul Koning
2006-04-26 14:55 ` Daniel Jacobowitz [this message]
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=20060426140821.GA20166@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=inderpreetb@gmail.com \
--cc=pkoning@equallogic.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