This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug python/16324] py-finishbreakpoint.c incorrect frame_id_eq
- From: "pmuldoon at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Mon, 24 Feb 2014 13:02:52 +0000
- Subject: [Bug python/16324] py-finishbreakpoint.c incorrect frame_id_eq
- Auto-submitted: auto-generated
- References: <bug-16324-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16324
Phil Muldoon <pmuldoon at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |pmuldoon at redhat dot com
Assignee|unassigned at sourceware dot org |pmuldoon at redhat dot com
--- Comment #1 from Phil Muldoon <pmuldoon at redhat dot com> ---
It seems the correct test here is to use frame_id_p which checks if a valid
stack is found (with a simple check to frame_id.stack_status !=
FID_STACK_INVALID). It also checks the frame_id is not an outer frame id.
There is no explicit check for a null_frame_id, which I found odd. get_frame_id
can return a null_frame_id, but lots of callers don't check the return so there
is a latent bug there too.
--
You are receiving this mail because:
You are on the CC list for the bug.