Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Kris Warkentin" <kewarken@qnx.com>
To: "Theodore A. Roth" <troth@openavr.org>
Cc: "Gdb@Sources.Redhat.Com" <gdb@sources.redhat.com>
Subject: Re: (remote) hellishly slow single stepping over library calls
Date: Fri, 16 May 2003 18:57:00 -0000	[thread overview]
Message-ID: <072601c31bdd$19bb8d30$0202040a@catdog> (raw)
In-Reply-To: <Pine.LNX.4.53.0305161134440.746@knuth.amplepower.com>

> Not sure if this is totally related (how does pdebug differ from rsp?)
> but maybe a solution could help avr users too.
>
> Some sort of optimization here would be boon for avr users. In our
> case we use gdb to talk to our avarice program
> (http://sourceforge.net/projects/avarice) which talks to a jtagice box
> which in turn talks to the actual target device via a jtag interface.
> Single stepping is painfully slow: step, wait 1-5 seconds, step, etc.
>
> The bottleneck for us not so much sending info over the wire via rsp,
> but in reading the registers from the device via jtag. If we could
> reduce the number registers that need to be read at each step, I think
> it could speed things up.

Well, once upon a time, we would get one register at a time.  Then we
decided to optimize and get the whole regset since we can supply them to gdb
and then it won't ask for any more.  The only place this really optimizes is
when you're asking for more than one per stop which isn't the case when
single stepping.  Like I said before though, in our case it might not matter
since we have to send a packet anyway and it costs no more to have the whole
regset in there.

You, however, I could see really benefitting from this if the jtag is
relatively slow at fetching registers and you have to do it one at a time.
There isn't any way to tell the jtag to send a whole set I suppose?

cheers,

Kris


  reply	other threads:[~2003-05-16 18:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-16 18:25 Kris Warkentin
2003-05-16 18:50 ` Theodore A. Roth
2003-05-16 18:57   ` Kris Warkentin [this message]
2003-05-16 19:15 ` Quality Quorum
2003-05-16 19:24   ` Kris Warkentin
2003-05-16 19:29     ` Daniel Jacobowitz
2003-05-16 20:04       ` Kris Warkentin
2003-05-16 23:10         ` Quality Quorum
2003-05-17  3:39       ` Andrew Cagney

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='072601c31bdd$19bb8d30$0202040a@catdog' \
    --to=kewarken@qnx.com \
    --cc=gdb@sources.redhat.com \
    --cc=troth@openavr.org \
    /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