bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug binutils/11527] New: addr2line does not display correct function na


From: dzidzitop at lavabit dot com
Subject: [Bug binutils/11527] New: addr2line does not display correct function name/filename/line for __libc_start_main (Linux/ELF)
Date: 22 Apr 2010 13:01:19 -0000

The application attached displays stacktrace of itself using execinfo.h tool
contributed with linux.

/home/liauchuk/projects/ddd/Debug/ddd [0x8048634]
/home/liauchuk/projects/ddd/Debug/ddd [0x8048602]
/lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe6) [0x21fb56]
/home/liauchuk/projects/ddd/Debug/ddd [0x8048561]

addr2line info:
address@hidden:~/projects/ddd/Debug$ addr2line -e ./ddd -f 0x21fb56
??
??:0

As it is visible, addr2line is not able to display proper information for the
__libc_start_main function despite of this information is available within DEBUG
info from the binary.

Also, looking at the internal BFD structures built from the binary, I've found
the the symbol element for this function is probably inconsistent. It's name
attribute contains "__libc_start_main@@GLIBC_2.0" and the
bfd_get_section_vma(abfd, symbol->section); returns zero as the starting address
for the section which this symbol belongs to. This could be a possible cause of
the problem

-- 
           Summary: addr2line does not display correct function
                    name/filename/line for __libc_start_main (Linux/ELF)
           Product: binutils
           Version: 2.21 (HEAD)
            Status: NEW
          Severity: minor
          Priority: P2
         Component: binutils
        AssignedTo: unassigned at sources dot redhat dot com
        ReportedBy: dzidzitop at lavabit dot com
                CC: bug-binutils at gnu dot org
  GCC host triplet: Linux2.6/GCC4.4.0
GCC target triplet: Linux2.6/GCC4.4.0/ELF


http://sourceware.org/bugzilla/show_bug.cgi?id=11527

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]