scan_prologue/next, misunderstanding
Joel Brobecker
brobecker@adacore.com
Tue May 19 13:33:00 GMT 2009
> I got inspiration from avr-tdep.c. I still have problems with 'next'.
> I set a 'printf' in the function skip_prologue and I can tell it is
> never used.
Just a first guess:
I haven't looked at the code itself, but there are usually more than one
unwinders; for instance, there is a dwarf unwinder that reads the frame
info data from the dwarf data and use that exclusively to do the unwinding.
This might explain why the AVR unwinder based on prologue analysis doesn't
get called.
--
Joel
More information about the Gdb
mailing list