This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
unavailable register
- From: "John S. Yates, Jr." <jyates at netezza dot com>
- To: "gdb" <gdb at sources dot redhat dot com>
- Date: Thu, 15 May 2003 12:52:34 -0400
- Subject: unavailable register
- Organization: Netezza Corporation
- Reply-to: "John S. Yates, Jr." <jyates at netezza dot com>
I have been implementing thread support in a remote
stub. My initial implementation provided only the
values of the registers.
I have now implemented register modification. One
small glitch is that some registers are either
architecturally readonly (eg: .sdata base register)
or simple do not exist (eg: a blocking call into the
scheduler does not save those registers that the
calling conventions indicate are destroyable).
My implementation of the 'P' message understands
these issue and returns a failure where appropriate.
Unfortunately, gdb's register cache seems to get
updated before the 'P' message returns success.
/john
--
John S. Yates, Jr. 508 665-6897 (voice)
Netezza Inc 508 665-6811 (fax)
200 Crossing Blvd. Framingham, MA 01701