From: Ramana Radhakrishnan <ramana.radhakrishnan@codito.com>
To: Chad Phillips <jcphillips@yahoo.com>
Cc: gdb@sources.redhat.com
Subject: Re: single-stepping remote target fails
Date: Thu, 23 Jun 2005 16:57:00 -0000 [thread overview]
Message-ID: <1119545687.15278.62.camel@localhost.localdomain> (raw)
In-Reply-To: <42BAD801.1000509@yahoo.com>
On Thu, 2005-06-23 at 11:40 -0400, Chad Phillips wrote:
> >On Thu, Jun 23, 2005 at 11:18:28AM -0400, Chad Phillips wrote:
> >> Problem 1.
> >> Single stepping in C source only steps by single machine instruction.
> >> I had expected that GDB might try to set breakpoints on the next
> >> instruction and then continue, but I see no such requests from GDB.
> >> How does GDB cause single steps through C (any high level language)
> >> source?
> >It does hardware single steps until the source line of the $pc changes.
>
> Interesting. It makes no requests to set breakpoints. If I explicitly
> set breakpoints, they work. But when I issue the step command, I get
> no breakpoint commands at my proxy application from GDB. Any Ideas?
Can your stub single step by itself without the debugger ? Guess you can
do with the JTAG on. Does your remote stub support the single stepping
packet ?
In any case do a set debug remote 1 just before you single step and
paste the output log over here. That could help answering.
cheers
Ramana
>
> >> Problem 2.
> >> When I issue the step command (or si, n, ni) to the target, GDB does
> >> a _lot_ of memory reads. It reads from the start of main up to the
> >> current PC (in main). What is it doing, and how can I make it stop?
>
> >Preumably it is doing prologue analysis. You need to work out (A) why
> >it triggered the prolgoue analyzer and (B) whether you should be using
> >unwind information instead of prologue analysis.
>
> Thanks. That make sense.
>
> -Chad
next prev parent reply other threads:[~2005-06-23 16:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-23 15:20 Chad Phillips
2005-06-23 15:25 ` Daniel Jacobowitz
2005-06-23 15:42 ` Chad Phillips
2005-06-23 16:16 ` Daniel Jacobowitz
2005-06-23 16:57 ` Ramana Radhakrishnan [this message]
2005-06-23 17:08 ` Chad Phillips
2005-06-23 19:13 ` Daniel Jacobowitz
2005-06-23 20:39 ` Chad Phillips
2005-06-23 20:43 ` Daniel Jacobowitz
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=1119545687.15278.62.camel@localhost.localdomain \
--to=ramana.radhakrishnan@codito.com \
--cc=gdb@sources.redhat.com \
--cc=jcphillips@yahoo.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).