From: Yao Qi <yao@codesourcery.com>
To: Tim Sander <tim@krieglstein.org>, <gdb@sourceware.org>
Subject: Re: gdb single stepping takes ages
Date: Wed, 18 Jun 2014 09:28:00 -0000 [thread overview]
Message-ID: <53A15B6A.8030803@codesourcery.com> (raw)
In-Reply-To: <2556774.80PXRilPAq@dabox>
On 06/18/2014 04:14 PM, Tim Sander wrote:
> Just after sending the mail recognized that the thread: "Remote Debugging with
> NEXT Command" touches a similar (the same?) issue. A solution mentioned was
> range checking. But in the openocd case it seems already enabled:
range stepping was added to improve the line stepping speed, but remote
stub (openocd in your case) has to support it.
> show range-stepping
> Debugger's willingness to use range stepping is on.
GDB can't do range stepping without stub's support. This command shows
the willingness of GDB to use range stepping, but if stub doesn't
support, GDB is still unable to do that. Please check your stub really
supports range stepping.
From the code or rsp level, the remote stub has to claim it supports
range stepping in the reply to vCont? ('r' in the reply), like this:
Sending packet: $vCont?#49...Packet received: vCont;c;C;s;S;t;r
Then, if we type command 'next', GDB will send "vCont;r"
Sending packet: $vCont;r80484cc,80484d7:p1cb0.1cb0;c#16...Packet
received: T0505:38eeffbf;04:c0ebffbf;08:d7840408;thread:p1cb0.1cb0;core:0;
--
Yao (é½å°§)
next prev parent reply other threads:[~2014-06-18 9:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 7:24 Tim Sander
2014-06-18 8:14 ` Tim Sander
2014-06-18 8:49 ` Agovic, Sanimir
2014-06-18 9:28 ` Yao Qi [this message]
2014-06-18 8:21 ` Mark Kettenis
2014-06-18 8:24 ` Luis Machado
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=53A15B6A.8030803@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=tim@krieglstein.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