This is the mail archive of the gdb-prs@sourceware.org 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]

[Bug python/16219] New: Frame.function returns wrong function


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

            Bug ID: 16219
           Summary: Frame.function returns wrong function
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: python
          Assignee: unassigned at sourceware dot org
          Reporter: tromey at redhat dot com

Based on my reading of frapy_function, I think it
returns the wrong function in the presence of inlining.
frapy_function uses find_pc_function to find the
function symbol.  However, find_pc_function calls
find_pc_sect_function, which ends with:

  return block_linkage_function (b);

That is, it skips inlined functions and returns
the enclosing non-inlined function.

That seems wrong to me.

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]