From: Tristan Wibberley <tristan.wibberley@gmail.com>
To: gdb@sourceware.org
Subject: Feature request: support a "resume previous execution" with a breakpoint commands section
Date: Wed, 25 Jul 2012 00:31:00 -0000 [thread overview]
Message-ID: <CADBfAvh8seSfev1zs6AMg=XFK9AU1BnjUg9UdwLNDD3ROv7WjQ@mail.gmail.com> (raw)
Please add a command that is valid within a breakpoint commands
section which simply resumes whatever you were doing (finish, next,
step, continue, until <location>, etc, as if you did not have the
extra breakpoint running some commands automatically).
Background:
It is possible to make gdb to take some action when a breakpoint is hit:
break <location>
commands
silent
some-actions
continue
end
The problem with this that the request will solve:
If you are using "next" to manually step through some code which will
also cause gdb to take those actions then your "next" command
magically turns into a full "continue". This happens also when the
code that will cause the actions to be taken is deeply nested and you
are expecting to step over it.
Please let me know if this request isn't described well.
Regards,
--
Tristan
next reply other threads:[~2012-07-25 0:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 0:31 Tristan Wibberley [this message]
2012-07-25 14:13 ` Tom Tromey
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='CADBfAvh8seSfev1zs6AMg=XFK9AU1BnjUg9UdwLNDD3ROv7WjQ@mail.gmail.com' \
--to=tristan.wibberley@gmail.com \
--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