scan_prologue/next, misunderstanding

[Tristan Gingold]

On May 19, 2009, at 3:33 PM, Joel Brobecker wrote:

>> 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.

[ Well the default debug format for avr is stabs... ]

The avr prologue analyzer is somewhat buggy and breaks the next  
command.  I have a patch to fix that
but didn't yet manage to submit it.  Will try next week.

Tristan.