From: "Sascha" <sascha@pasalacqua.de>
To: <gdb@sourceware.org>
Subject: How to interrupt a stepping GDB ?
Date: Mon, 19 Jun 2006 02:13:00 -0000 [thread overview]
Message-ID: <20060619021300.UsX3cQ9REekKG3E7oY7IiZNuxzcowl0NDfxfR_8i-zs@z> (raw)
Hello,
I've got a question about GDB and the "next/step" command.
Situation:
The debugger stopped at the C instruction:
"for (; a; --a);"
This is a simple loop counting down to zero.
If you "next", GDB will step through that loop until a == 0.
On a local, fast machine this might be okay. But on a (slow) remote target,
stepping a loop like this will take minutes or hours because GDB sends
thousands or even millions of step commands until a == 0;
Now the question: If I notice such a case - how can I interrupt GDB? If I
notice that the stepping would take a long time I'd rather interrupt GDB and
set a breakpoint on the next line. CTRL-C does not work. And waiting hours
or shutting down GDB is no acceptable.
Thanks
Sascha
next reply other threads:[~2006-06-18 9:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 2:13 Sascha [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-20 12:24 Daniel Jacobowitz
2006-07-03 18:28 ` Jim Blandy
2006-07-03 19:20 ` Mark Kettenis
2006-06-19 2:13 Sascha
2006-06-19 2:13 Sascha
2006-06-19 2:13 Sascha
2006-06-19 2:13 Sascha
2006-06-19 2:13 Sascha
2006-06-19 2:13 Sascha
2006-06-19 2:13 Sascha
2006-06-19 2:13 Sascha
2006-06-19 2:13 Sascha
2006-06-19 2:13 Sascha
2006-06-19 2:13 Sascha
2006-06-19 2:13 Sascha
2006-06-19 2:13 Sascha
2006-06-19 2:13 Sascha
2006-06-19 2:13 Sascha
2006-06-19 2:13 Sascha
2006-06-19 2:13 Sascha
2006-06-19 2:13 Sascha
2006-06-19 2:13 Sascha
2006-06-19 2:13 Sascha
2006-06-19 2:13 Sascha
2006-06-19 2:13 Sascha
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=20060619021300.UsX3cQ9REekKG3E7oY7IiZNuxzcowl0NDfxfR_8i-zs@z \
--to=sascha@pasalacqua.de \
--cc=gdb@sourceware.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