This is the mail archive of the gdb@sourceware.org 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]

"Preprocess" dwarf info?


Hi

I'm now trying out stabs and dwarf debug info. With stabs all gdb symbols
get filled with data like type (LOC_STATIC, LOC_REGISTER etc) and
values (SYMBOL_VALUE, SYMBOL_VALUE_ADDRESS). If the symbol
gets evaluated only few target accesses are needed (registers, memory)
for the final value.

With dwarf this info is not stored expressively anymore if a symbol
is of type LOC_COMPUTED or LOC_COMPUTED_ARG. Instead gdb will
evaluate the dwarf debug "code" to return the value every time. I know
that there may be symbol "locations" that are not representable with
just 1 or 2 values. But still values such as register numbers or offsets
will always be the same.

So is there a way to somehow "preprocess" the dwarf info to get out
the same info gdb stores when using the stabs info?

Thanks

bye  Fabi 



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