This is the mail archive of the
mailing list for the GDB project.
Re: think-o: dwarf2 CFA != frame->frame (x86-64)
- From: Andrew Cagney <ac131313 at cygnus dot com>
- To: Daniel Berlin <dan at dberlin dot org>
- Cc: gdb at sources dot redhat dot com
- Date: Tue, 09 Apr 2002 15:17:40 -0400
- Subject: Re: think-o: dwarf2 CFA != frame->frame (x86-64)
- References: <Pine.LNX.firstname.lastname@example.org>
>> Please re-read what I wrote.
> You said " The problem is that this algorithm assumes that each frame uses
> the same mechanism for locating register values. With
> the introduction of dwarf2cfi, this is no longer
> true. Some frames may use the debug info while others may use the
> old prologue analysis technique.
> You are incorrect.
We're going to have to agree to disagree.
> It's an either-or case. Never is their a mixture of methods, unless you do
> something illegal.
If GDB decides to do what you state, it will be incapable of unwinding
through libraries (where there is no debug info).
I think that is a significant feature loss and one I don't consder
I see no reason why GDB shouldn't act ``illegally'' and use the
traditional prolog scanner as a fallback to debug info.