gdb/466: compute get_saved_register recursively - handle mixed frames

[ac131313 at redhat dot com]

>Number:         466
>Category:       gdb
>Synopsis:       compute get_saved_register recursively - handle mixed frames
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Sat Apr 06 06:38:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     ac131313@redhat.com
>Release:        2002-04-05
>Organization:
>Environment:

>Description:
At present the *_get_saved_register() code uses an iterative algorithm (running up the stack) to find the saved register value.

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.

The ``fix'' is to recursively request the register value thus allowing each frame to decide, locally, how to obtain a saved register value.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: