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: 11 Oct 2009 03:09:04 -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-11 03:09 -------
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-10 02:42 -------
> I think add a switch for prec to close record in call() can handle it.
>
> Do you think it's OK?
>
> Michael, what do you think about it?
Well, this actually brings up a number of related questions.
What if, during the recording, the user makes changes such as:
* Change memory
* Change registers
* Change the course of execution, eg. by
- change the PC
- "jump" command
- "call" command
I think if user changes memory or registers, you record that.
Right?
And if user changes PC, or uses "jump" command, we will
record it also, right?
So in that case, it seems like we should also record the
"call" command.
--
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.