From: Luis Machado <lgustavo@codesourcery.com>
To: Tim Sander <tim@krieglstein.org>, <gdb@sourceware.org>
Subject: Re: gdb single stepping takes ages
Date: Wed, 18 Jun 2014 08:24:00 -0000 [thread overview]
Message-ID: <53A14CC1.9070602@codesourcery.com> (raw)
In-Reply-To: <11141246.9lllTVUqLL@dabox>
On 06/18/2014 08:24 AM, Tim Sander wrote:
> Hi
>
> I am currently using openocd as a gdbserver backend for debugging an embedded
> target with gdb 7.7. When i want to step over a single line with -exec-next:
>
> for(int a=0; a<1000000;a++){ };
>
> the time taken for the step is linear to the maximum count number and takes in
> my setup about 1 second for one increment of a. Setting a temp breakpoint in
> the next line and continuing works much faster.
>
> So is there a way improve the stepping speed in such situations?
>
> Best regards
> Tim
>
>
In that case i'd use "until <line number>" to skip the loop. Stepping
through the loop *will* take a long time since GDB instruction-steps its
way out of there (for reasons explained in the Remote Debugging mail you
mentioned in the other mail).
Luis
prev parent reply other threads:[~2014-06-18 8:24 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
2014-06-18 8:21 ` Mark Kettenis
2014-06-18 8:24 ` Luis Machado [this message]
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=53A14CC1.9070602@codesourcery.com \
--to=lgustavo@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