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: "guosheng_gao at realsil dot com.cn" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Wed, 13 Nov 2013 03:10:11 +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 #7 from ggs334 <guosheng_gao at realsil dot com.cn> ---
>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 right! this issue only triggers when debugging assembler code!
--
You are receiving this mail because:
You are on the CC list for the bug.