[Bug general/3863] libunwind occasionally does not return frame function names.

["jan dot kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org>]

------- Additional Comments From jan dot kratochvil at redhat dot com  2007-01-12 11:26 -------
Disowning this Bug as it is not libunwind related.

libunwind only fails to resolve the symbols after the fd (file descriptor)
process table gets filled up (>1024 fds).

You can debug it by:
valgrind --track-fds=yes ./frysk-core/TestRunner -r 1000
'testStressMultiThreadedDetach(frysk.util.StressTestFStack)'

resulting in libunwind's failings:
Warning: invalid file descriptor 1019 in syscall open()

and the final reported leaked fds:
Open file descriptor 178: /lib/libc-2.5.so
   at 0x40515C2: open64 (open64.c:45)
   by 0x85A5E5A: dwfl_linux_proc_find_elf (linux-proc-maps.c:297)
   by 0x85A407D: find_file (dwfl_module_getdwarf.c:103)
   by 0x85A4B71: find_dw (dwfl_module_getdwarf.c:395)
   by 0x85A4CC6: dwfl_module_getdwarf (dwfl_module_getdwarf.c:462)
   by 0x85AADB2: dwfl_module_getsrc (dwfl_module_getsrc.c:57)
   by 0x85A6CA3: dwfl_getsrc (dwfl_getsrc.c:55)
   by 0x8161192: _ZN3lib2dw4Dwfl11dwfl_getsrcEJxx (Dwfl.cxx:138)
   by 0x81583B6: _ZN3lib2dw4Dwfl13getSourceLineEJPNS0_8DwflLineEx (Dwfl.java:110)
   by 0x8133C36: frysk::rt::StackFrame::StackFrame(lib::unwind::FrameCursor*,
frysk::proc::Task*, frysk::rt::StackFrame*) (StackFrame.java:127)
   by 0x8133952:
_ZN5frysk2rt12StackFactory16createStackFrameEJPNS0_10StackFrameEPNS_4proc4TaskEi
(StackFactory.java:79)
   by 0x8133AB4:
_ZN5frysk2rt12StackFactory16createStackFrameEJPNS0_10StackFrameEPNS_4proc4TaskE
(StackFactory.java:112)

Open file descriptor 177: /usr/lib/debug/lib/ld-2.5.so.debug
   at 0x40515C2: open64 (open64.c:45)
   by 0x85A501E: try_open (find-debuginfo.c:79)
   by 0x85A53D4: dwfl_standard_find_debuginfo (find-debuginfo.c:178)
   by 0x85A45AF: find_debuginfo (dwfl_module_getdwarf.c:178)
   by 0x85A4BEA: find_dw (dwfl_module_getdwarf.c:417)
   by 0x85A4CC6: dwfl_module_getdwarf (dwfl_module_getdwarf.c:462)
   by 0x85AADB2: dwfl_module_getsrc (dwfl_module_getsrc.c:57)
   by 0x85A6CA3: dwfl_getsrc (dwfl_getsrc.c:55)
   by 0x8161192: _ZN3lib2dw4Dwfl11dwfl_getsrcEJxx (Dwfl.cxx:138)
   by 0x81583B6: _ZN3lib2dw4Dwfl13getSourceLineEJPNS0_8DwflLineEx (Dwfl.java:110)
   by 0x8133C08: frysk::rt::StackFrame::StackFrame(lib::unwind::FrameCursor*,
frysk::proc::Task*, frysk::rt::StackFrame*) (StackFrame.java:125)
   by 0x8133B12: frysk::rt::StackFrame::StackFrame(lib::unwind::FrameCursor*,
frysk::proc::Task*) (StackFrame.java:92)


There is some leakage, libdwfl's dwfl_end() is not called appropriately.
As it is called from the Dwfl binding's finalize() I assume there are some
leaked Java object references.
But I did not analyse it more as the bug looks to lie in the Java land.
Also running of the testcase above eats about 0.5GB of memory also suggesting
some leakage occurs there.


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|jan dot kratochvil at redhat|frysk-bugzilla at sourceware
                   |dot com                     |dot org


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

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.