This is the mail archive of the gdb@sourceware.cygnus.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: IA32: printing FP register variables


>>>>> "Michael" == Michael Meissner <meissner@cygnus.com> writes:

Michael> This is actually a symptom of a much deeper problem that I
Michael> would like to see addressed in the compiler at some point,
Michael> namely tracking variables being reloaded, etc.  For example,
Michael> if the compiler determines that a variable is on the stack,
Michael> but needs to load up a variable into a register to work on it
Michael> (reload in gcc speak), we currently don't track this, so if
Michael> you put a breakpoint after the load has been done, but before
Michael> it is used, you won't be able to change the value to affect
Michael> the running of the program.

FWIW this is the also sort of information you need to build tables for
a precise garbage collector.  A precise GC needs to know when a
pointer (even a disguised one) has been loaded into a register, or
spilled to the stack.

Tom

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