From: "Juraj Oršulić" <juraj.orsulic@fer.hr>
To: <gdb@sourceware.org>
Subject: "continue" in breakpoint commands breaks line-by-line stepping
Date: Fri, 10 Mar 2017 08:25:00 -0000 [thread overview]
Message-ID: <CAEPqvoxrAf9a2kWd92+AnB--VUVnQHrty9ovtgs1p4J5vtZyfA@mail.gmail.com> (raw)
Hi everyone, I have a quick question. I have added some breakpoint
commands for logging using the "commands" command. Since I don't want
to stop the execution in these points, I added a "continue", as
mentioned in https://sourceware.org/gdb/onlinedocs/gdb/Break-Commands.html.
However, this breaks stepping line-by-line in outer frames - if I
stumple upon one of these logging breakpoints, it issues a "continue",
and I lose control if I call "next" when I am in an outer frame. How
could I mitigate this? Perhaps by redefining "next" to set a temporary
breakpoint on the next line to ensure that I stop there? Should this
be the default behavior?
Thanks,
Juraj
next reply other threads:[~2017-03-10 8:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 8:25 Juraj Oršulić [this message]
2017-03-16 8:58 ` Tom Tromey
2017-03-16 12:53 ` Tom Tromey
[not found] ` <51b1626e27124e7f9b43603f0bb2a4dc@MAIL.fer.hr>
2017-03-16 12:21 ` Juraj Oršulić
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=CAEPqvoxrAf9a2kWd92+AnB--VUVnQHrty9ovtgs1p4J5vtZyfA@mail.gmail.com \
--to=juraj.orsulic@fer.hr \
--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