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: "msnyder at vmware dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: 12 Oct 2009 22:38:37 -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 msnyder at vmware dot com 2009-10-12 22:38 -------
Subject: Re: replay mode should not or only optionally
enter code executed by call()
teawater at gmail dot com wrote:
> ------- Additional Comments From teawater at gmail dot com 2009-10-12 07:15 -------
> If the call() call the function that will not change the global value (some
> memory), it will change the most of registers (for example: pc) to the value
> before call().
>
Oh yeah, sorry, I mis-understood you. I thought you were talking
about record mode.
Yes, during replay mode, any "call" will certainly fail.
But I don't worry about it, because, well, it will fail.
Call will try to change the PC, as you say, and that will
error out.
You would like to catch the error earlier?
--
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.