This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap 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 dyninst/20052] pthreadprobes.exp stall


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

Martin Cermak <mcermak at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jistone at redhat dot com

--- Comment #1 from Martin Cermak <mcermak at redhat dot com> ---
Interestingly, using distribution systemtap-2.8-10.el7.x86_64 on the very same
rhel7 test box reliably gives a segfault (which may easily be completely
different issue of course). 

=======
# stap --dyninst  xxx.stp -c ./pthreadprobes
stapdyn: WARNING: Couldn't find an instrumentation point at 0x7f16781863c8,
/usr/lib64/libpthread-2.17.so+0xa3c8
stapdyn: WARNING: Couldn't find an instrumentation point at 0x7f16781868c7,
/usr/lib64/libpthread-2.17.so+0xa8c7
stapdyn: WARNING: Couldn't find an instrumentation point at 0x7f16781869f7,
/usr/lib64/libpthread-2.17.so+0xa9f7
stapdyn: WARNING: Couldn't instrument the function containing 0x7f16781862df,
/usr/lib64/libpthread-2.17.so+0xa2df
WARNING: /usr/bin/stapdyn exited with signal: 11 (Segmentation fault)
Pass 5: run failed.  [man error::pass5]
#
=======

Two corefiles are generated, but gdb isn't very happy about those distort bad
boys. One comes from stapdyn and doesn't seem to be useful. The other comes
from the pthreadprobes binary and shows sort of traceback (probably not too
valuable though):

=======
Core was generated by `./pthreadprobes'.
Program terminated with signal 11, Segmentation fault.
#0  0x0000000000000000 in ?? ()
(gdb) bt
#0  0x0000000000000000 in ?? ()
#1  0x00007f21de51c8ce in DYNINSTstaticHeap_16M_anyHeap_1 () from
/usr/lib64/dyninst/libdyninstAPI_RT.so.8.2
#2  0x0000000000000000 in ?? ()
(gdb) 
=======

Another SEGV of the same testcase is PR17245.

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

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