This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/1160: Add function check to frame_id_eq()
- From: ac131313 at redhat dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 30 Mar 2003 17:09:59 -0000
- Subject: gdb/1160: Add function check to frame_id_eq()
- Reply-to: ac131313 at redhat dot com
>Number: 1160
>Category: gdb
>Synopsis: Add function check to frame_id_eq()
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: maintenance
>Submitter-Id: net
>Arrival-Date: Sun Mar 30 17:18:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: ac131313 at redhat dot com
>Release: unknown-1.0
>Organization:
>Environment:
>Description:
frame_id_eq() et.al. need to use the frame's function in any comparison.
Unfortunatly it isn't a simple case of throwing the switch.
The frame code needs to first start initializing the ID.func_addr with something sensible (at present it contains the frame's PC. Ulgh!).
Trying to get frame_id_eq() to map the PC onto the FUNC addr also doesn't work as, for dummy frames, that is the last thing that should be done (the FUNC is the address of a breakpoint on the stack).
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: