This is the mail archive of the gdb@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]
Other format:	[Raw text]

Re: GDB caching question

From: Andrew Cagney <ac131313 at redhat dot com>
To: "Yadav, Vikas" <Vikas dot Yadav at netapp dot com>
Cc: gdb at sources dot redhat dot com
Date: Fri, 27 Jun 2003 10:04:03 -0400
Subject: Re: GDB caching question
References: <A14D796A8FBC5A4FB7A674384E324CB4D368A4@burgundy-fe.eng.netapp.com>

When I set $fp or $pc varibles in gdb for i386, it sometime does not work. Does anyone else have done something like this. In my case if I do a backgrace following by modification to $fp and $pc to change my stack, it does not work. However If I don't do a "backtrace" first, it works. I suspect some kind of caching of register value is cause of this behaviour.

Any insight here ?

GDB is _ment_ to flush all caches after any change to the target. Sounds like this isn't happening (there was another post related to this a week or so back).

Suggest setting break point on all the *changed* methods and see if/when they are called.

Andrew

PS: Note that the intent is to replace the lot by replacing a target changed event to the observer.

References:
- GDB caching question
  - From: Yadav, Vikas

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