This is the mail archive of the gdb-prs@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]

gdb/631: Eliminate find_saved_register()


>Number:         631
>Category:       gdb
>Synopsis:       Eliminate find_saved_register()
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Mon Aug 05 21:18:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     ac131313@redhat.com
>Release:        2002-08-05
>Organization:
>Environment:

>Description:
The [broken] function find_saved_register() doesn't use the new recursive register unwind code when running over the stack.

More interesting though is that three of the four architectures (ns32k, vax, alpha) that use it (via a custom XXX_get_saved_register()) would appear to not even need the custom get saved register and hence can eliminate their call.

That just leaves the call in the MIPS.  That should be changed to use frame_register_unwind() if not something else.


>How-To-Repeat:

>Fix:

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


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