From: John Gilmore <gnu@toad.com>
To: Ender Dai <xdai@uoregon.edu>
Cc: "Abid\, Hafiz" <Hafiz_Abid@mentor.com>,
"gdb\@sourceware.org" <gdb@sourceware.org>
Subject: Re: gdb behavior on tight loop
Date: Wed, 24 Jul 2013 21:17:00 -0000 [thread overview]
Message-ID: <201307242116.r6OLGhgN015774@new.toad.com> (raw)
In-Reply-To: <87mwpbq3a8.fsf@cortana.d.cs.uoregon.edu>
> >> Please see the gdb session below. When I run "next" on line 5, the tight
> >> loop, it will take several seconds before gdb stop on line 6 and I regain
> >> control.
> >>
> >> If I set an additional breackpoint on line 6, and "continue" on line 5 instead
> >> of "next", everything looks good.
In situations like this, the "until" command is convenient.
You can say "u 6" and gdb will set a temporary breakpoint at line 6,
run the program at full speed until it hits that breakpoint (or some
other breakpoint or error) and then remove the temporary breakpoint.
John Gilmore
prev parent reply other threads:[~2013-07-24 21:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 3:51 Ender Dai
2013-07-24 12:23 ` Abid, Hafiz
2013-07-24 17:25 ` Ender Dai
2013-07-24 21:17 ` John Gilmore [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=201307242116.r6OLGhgN015774@new.toad.com \
--to=gnu@toad.com \
--cc=Hafiz_Abid@mentor.com \
--cc=gdb@sourceware.org \
--cc=xdai@uoregon.edu \
/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