This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug dyninst/14637] New: using dyninst, probing pthread mutex markers can hang the process
- From: "dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Thu, 27 Sep 2012 20:19:23 +0000
- Subject: [Bug dyninst/14637] New: using dyninst, probing pthread mutex markers can hang the process
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=14637
Bug #: 14637
Summary: using dyninst, probing pthread mutex markers can hang
the process
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: dyninst
AssignedTo: systemtap@sourceware.org
ReportedBy: dsmith@redhat.com
Classification: Unclassified
When using --runtime=dyninst, probing the pthread mutex markers can hang the
process.
The test script I'm using is a modified version of the test from
systemtap.exelib/pthreadprobes.exp. I've modified that testcase to use
statistics as counters.
What I believe is going on is that the systemtap stat code uses pthread mutexes
internally, Since that test puts probes on the mutex markers, systemtap is
getting "internal" probe hits (possibly causing the program to infinitely
loop).
We may have to somehow ignore those hits or blacklist those markers and pthread
library routines.
(I've got a patch I'm testing patch that changes the mutexes to rwlocks, but
that just lessens the problem a bit.)
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.