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]

call frames


Hi all,
I met a following problem while fixing gdb to pass gdb.asm testsuite on x86-64: When building a backtrace I depend on Dwarf-2 informations from .debug_frame or .eh_frame. Unfortunately hand-written assembler sources usually don't provide these sections and thus I can't do backtrace the standard way. Now what to do?

Should I have a fall-back FDE for functions that don't provide their own one and try to use it, assuming the function has a valid prologue (eg. push %rbp; mov %rbp,%rsp)? This seems to be quite a reasonable solution.

Another way would be disabling these tests in testsuite/gdb.asm for x86-64 paltform ;-)

Comments?

Michal Ludvig
--
* SuSE CR, s.r.o * mludvig@suse.cz
* +420 2 9654 5373 * http://www.suse.cz



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