This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/11557] Stale register and frame info in non-stop/async modes, just after resuming a thread
- From: "pedro at codesourcery dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: 29 Apr 2010 14:35:40 -0000
- Subject: [Bug gdb/11557] Stale register and frame info in non-stop/async modes, just after resuming a thread
- References: <20100429143425.11557.pedro@codesourcery.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From pedro at codesourcery dot com 2010-04-29 14:35 -------
The problem is that we ended up with a stale regcache after resuming
the thread. Any stop (internal or visible to the user) would flush
the cache, and so would a few user commands, like "info threads", but
iff you have more than one thread.
The always-works workaround, is to force a register cache
flush with "flushregs":
(gdb) flushregs
Register cache flushed.
(gdb) info threads
* 1 process 11017 (running)
(gdb) p $pc
Target is executing.
(gdb) frame
No stack.
("No stack" is bit of a lie in this case, but better than stale info!)
--
http://sourceware.org/bugzilla/show_bug.cgi?id=11557
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.