This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/16157] the function get_pc_function_start (CORE_ADDR pc) maybe inaccurate
- From: "palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 12 Nov 2013 14:29:20 +0000
- Subject: [Bug gdb/16157] the function get_pc_function_start (CORE_ADDR pc) maybe inaccurate
- Auto-submitted: auto-generated
- References: <bug-16157-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16157
--- Comment #5 from Pedro Alves <palves at redhat dot com> ---
> Unless, again, this is really the outer_frame_id bits triggering.
> outer_frame_id really should die...
BTW, if this is the case, this means that this issue only triggers when
stepping through code in the outermost frame (the entry point). IOW, iIf your
_start was actually some other function that was called by _start (so that
it'd wouldn't be the outermost frame), this issue wouldn't trigger.
--
You are receiving this mail because:
You are on the CC list for the bug.