public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "andre dot poenitz at nokia dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug backtrace/10689] New: replay mode should not or only optionally enter code executed by call()
Date: Wed, 23 Sep 2009 12:20:00 -0000 [thread overview]
Message-ID: <20090923122042.10689.andre.poenitz@nokia.com> (raw)
Reverse execution currently also steps into code that was 'manually' executed
using 'call'. That is unfortunate in situations where 'calls' are used in an
automated way (like a stop hook, or initiated by a front end). It would be nice
if the tracking of the call execution could be temporarily (or globally) disabled.
--
Summary: replay mode should not or only optionally enter code
executed by call()
Product: gdb
Version: unknown
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: backtrace
AssignedTo: unassigned at sourceware dot org
ReportedBy: andre dot poenitz at nokia dot com
CC: gdb-prs at sourceware dot org,teawater at gmail dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=10689
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2009-09-23 12:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 12:20 andre dot poenitz at nokia dot com [this message]
2009-09-24 3:00 ` [Bug backtrace/10689] " teawater at gmail dot com
2009-09-24 15:41 ` andre dot poenitz at nokia dot com
2009-09-27 2:54 ` teawater at gmail dot com
2009-09-28 6:44 ` andre dot poenitz at nokia dot com
2009-10-10 2:42 ` teawater at gmail dot com
2009-10-11 3:09 ` msnyder at vmware dot com
2009-10-12 7:15 ` teawater at gmail dot com
2009-10-12 22:38 ` msnyder at vmware dot com
2009-10-13 6:11 ` teawater at gmail dot com
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=20090923122042.10689.andre.poenitz@nokia.com \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).