From: Daniel Jacobowitz <drow@false.org>
To: Deepak Saxena <dsaxena@plexity.net>
Cc: gdb@sources.redhat.com
Subject: Re: Remote stub can't single-step, how to tell GDB?
Date: Thu, 12 Aug 2004 22:36:00 -0000 [thread overview]
Message-ID: <20040812223628.GA21314@nevyn.them.org> (raw)
In-Reply-To: <20040812214958.GA6063@plexity.net>
On Thu, Aug 12, 2004 at 02:49:58PM -0700, Deepak Saxena wrote:
>
> Hello,
>
> I am working on porting the existing ARM KGDB stub into the
> grand-unified-kgdb project (http://kgdb.sf.net) and am looking
> for some info on how to cleanup our single-step handling. For
> the existing stub we basically took the get_next_pc() code
> from gdb and put it in the kgdb-stub so that we can execute
> single-steps in the stub itself. When we receive an 's' command,
> we call get_next_pc() and stuff the breakpoint at that address.
> IMHO, having this in the kernel is overkill and skimming the gdb src,
> I am guessing there is away to just force the user's client to do this,
> but I am not sure how. In arm-tdep.c, I see the following comment that
> makes me wonder if right now I have no choice but handle single-step
> in the kernel stub:
>
> /* Single stepping. */
> /* XXX For an RDI target we should ask the target if it can single-step. */
> set_gdbarch_software_single_step (gdbarch, arm_software_single_step);
>
> Any pointers appreciated.
Hi Deepak :-)
Does GDB currently send single-step packets to the kgdb stub? What
version of GDB are you using? The call to set_gdbarch_software_single_step
sets up software (client-GDB-controlled) single stepping, and it should
not ask the stub to do so.
[GDB's handling of target capabilities in this area is a bit shoddy.
But here it looks like the default matches what you want anyway.]
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-08-12 22:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 21:50 Deepak Saxena
2004-08-12 22:36 ` Daniel Jacobowitz [this message]
2004-08-12 23:08 ` Deepak Saxena
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=20040812223628.GA21314@nevyn.them.org \
--to=drow@false.org \
--cc=dsaxena@plexity.net \
--cc=gdb@sources.redhat.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