This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug uprobes/13663] New: automate sdt semaphores
- From: "jistone at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Fri, 03 Feb 2012 23:00:19 +0000
- Subject: [Bug uprobes/13663] New: automate sdt semaphores
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=13663
Bug #: 13663
Summary: automate sdt semaphores
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: uprobes
AssignedTo: systemtap@sourceware.org
ReportedBy: jistone@redhat.com
Classification: Unclassified
A few months ago, we had some discussion about SDT probes automatically dealing
with semaphores in the app itself. See this thread:
http://sourceware.org/ml/systemtap/2011-q3/msg00388.html
In such a design, there wouldn't really be a semaphore counter at all. The
ENABLED() macro would basically be a predicate on whether the probe IP has been
modified from a nop to a debug trap. But do read that message thread for some
anticipated complications.
Hopefully we could do this without any change to the SDT ABI. To consumers, it
would just look like a probe point without any semaphore.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.