From: Miles Bader <miles@gnu.org>
To: gdb@sources.redhat.com
Subject: Re: emulating single-step in gdbserver?
Date: Thu, 20 Feb 2003 15:53:00 -0000 [thread overview]
Message-ID: <20030220155332.GA29101@gnu.org> (raw)
In-Reply-To: <20030220150813.GA28933@nevyn.them.org>
Thanks for the response.
It looks like I won't need to do this after all -- I've been informed that
the CPU _does_ implement single-stepping, it's just that the documentation
claims otherwise to avoid having to support it (and all the other debugger
writers use it, so it works)!
> > A related question, BTW, is what's the precise meaning of
> > `the_low_target.breakpoint_reinsert_addr'? It's not documented very
> > well...
>
> It's essentially a very limitted next_pc function. The only
> breakpoints gdbserver places right now are in empty marker functions in
> the thread library. After hitting one, it either single-steps or
> places a breakpoint at the function's return address, and then
> reinserts it. The advantage is that finding the return address is
> quick and very simple.
I see. Now the comments that are there make a bit more sense; I was very
confused when I saw the mips just returned the function's return-address!
I guess I can just set it to null and let gdb single-step over the
breakpoint.
Thanks,
-Miles
--
Next to fried food, the South has suffered most from oratory.
-- Walter Hines Page
next prev parent reply other threads:[~2003-02-20 15:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 4:39 Miles Bader
2003-02-20 13:07 ` Andrew Cagney
2003-02-20 15:08 ` Daniel Jacobowitz
2003-02-20 15:53 ` Miles Bader [this message]
[not found] ` <miles@lsi.nec.co.jp>
2003-02-20 15:31 ` Kevin Buettner
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=20030220155332.GA29101@gnu.org \
--to=miles@gnu.org \
--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