This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug backtrace/10689] replay mode should not or only optionally enter code executed by call()
- From: "andre dot poenitz at nokia dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: 28 Sep 2009 06:44:48 -0000
- Subject: [Bug backtrace/10689] replay mode should not or only optionally enter code executed by call()
- References: <20090923122042.10689.andre.poenitz@nokia.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From andre dot poenitz at nokia dot com 2009-09-28 06:44 -------
I use call() to extract information from the inferior after each stop (be it
triggered by a breakpoint or by stepping). The result is pretty much what the
Python pretty printers do, except that the code is run natively in the inferior
and I therefore do not have to deploy Python. With call() activity being
recorded I am basically unable to step backwards as I always end up in my
helper code.
--
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.