[Bug gdb/16157] the function get_pc_function_start (CORE_ADDR pc) maybe inaccurate

["palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=16157

--- Comment #8 from Pedro Alves <palves at redhat dot com> ---
I feels like you're either ignoring half my suggestions, or not reading
carefully.  It makes it hard for me to help you.

> > What's different between lop3 and lop2? 
>No different from lop2 and lop3, only 2 labels.

I'm well aware they're too labels.  But what makes it so that for instructions
between lop3 and lop2, gdb believes the function is _start, not lop3?

You still haven't checked for outer_frame_id.

> >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!

Sure, except that's not what I said.

-- 
You are receiving this mail because:
You are on the CC list for the bug.