[Please reply to the list, thanks!]
On Mon, Feb 04, 2008 at 09:35:07PM +0000, Greg Law wrote:
When a register is examined, we (eventually) get to
frame_register_unwind. This does:
frame->unwind->prev_register (frame->next, &frame->prologue_cache, regnum,
optimizedp, lvalp, addrp, realnump, bufferp);
which is actually a function pointer to (on plain old x86 Linux)
sentinel_frame_prev_register, which goes:
Ah yes. That's the only prologue cache which has any business
accessing a regcache directly, none of the others do.
flushregs should invalidate the frame cache and current/selected
frame. I have been meaning to fix that for, roughly, ever. Does
it work better if you do that?