This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: [PATCH]: New maintainer command "flushregs"


Steven Johnson wrote:

> The problem is, after a hardware Reset, all the registers have changed
> but GDB does not know it. GDB Never looses connection to the target
> because I am using a BDM Interface. So If I then try and re-set the
> watchdog and debug registers using GDB, GDB thinks they have already
> been set and refuses to change them.

I'd think of this as a (design) bug in GDB.  I think that there should
be mechanism that allows the target/backend to notify GDB that the
targets state has just been trashed.

> Also, do you know how one goes about turning $regname into a register
> number? I haven't found this yet?

grep for REGISTER_NAME.  GDB does a linear search through the
REGISTER_NAME table - see parse.c:target_map_name_to_register().

	enjoy,
		Andrew

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]