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]

backtrace/1311: Audit get_frame_pc vs get_frame_address_in_block

From: ac131313 at redhat dot com
To: gdb-gnats at sources dot redhat dot com
Date: 4 Aug 2003 12:31:04 -0000
Subject: backtrace/1311: Audit get_frame_pc vs get_frame_address_in_block
Reply-to: ac131313 at redhat dot com

>Number:         1311
>Category:       backtrace
>Synopsis:       Audit get_frame_pc vs get_frame_address_in_block
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          maintenance
>Submitter-Id:   net
>Arrival-Date:   Mon Aug 04 12:38:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     ac131313@redhat.com
>Release:        unknown-1.0
>Organization:
>Environment:

>Description:
There are many cases where get_frame_address_in_block (which handles the end-of-function edge case) should be used instead of get_frame_pc.

For instance, get_frame_func should use address_in_block since it needs to find this, and not the adjacent, frame's function.

(I'm posting a patch for that one but I bet there are many many other cases of the same problem)
>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]