[PATCH] Don't attach to 'target_changed' observer in regcache

Pedro Alves palves@redhat.com
Tue Aug 21 19:39:00 GMT 2012


On 08/09/2012 09:36 AM, Yao Qi wrote:
> I am thinking that we may add a new gdbarch hook function 'register_changed 
> (int regnum)'.  In default, it invalidates all regcaches, and backend can 
> override it to do something optimally.  At least, we don't have to invalidate 
> all regcache on some ports, such as x86, tic6x.

gdbarch is only useful for the cases gdb can hardcode.  it is not
sufficient in the cases the target feeds gdb a target description with
more registers than gdb knows the core architecture of the running
target has.

-- 
Pedro Alves



More information about the Gdb-patches mailing list