From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/6880] New: more syntax for shared library probing
Date: Fri, 12 Sep 2008 14:00:00 -0000 [thread overview]
Message-ID: <20080912135907.6880.fche@redhat.com> (raw)
While the current uprobes syntax can support shared libraries
probe process("/lib/.....so").... { }
it may be helpful to add some more syntax:
This would resolve the exact library file via heuristics like ldd,
and constrain the uprobes to only named processes.
probe process("ls").library("libc").function/statement(...) { }
This would search LD_LIBRARY_PATH / /etc/ld.so.conf* for the library
instead of $PATH as for an executable. Though perhaps we could do
this automatically if the process file name matches "lib*". Such a
probe could expand to multiple libraries (/lib64 and /lib variants
for example).
probe library("libc").function/statement(...) { }
--
Summary: more syntax for shared library probing
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: fche at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=6880
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2008-09-12 14:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 14:00 fche at redhat dot com [this message]
2008-12-11 16:59 ` [Bug translator/6880] " fche at redhat dot com
2009-04-22 18:44 ` mjw at redhat dot com
2009-04-22 18:47 ` fche at redhat dot com
2009-05-06 9:51 ` mjw at redhat dot com
2009-05-06 19:30 ` jistone at redhat dot com
2009-05-20 20:30 ` cap at nsc dot liu dot se
2009-06-11 11:28 ` srikar at linux dot vnet dot ibm dot com
2009-10-29 23:50 ` jistone at redhat dot com
2009-11-17 16:39 ` scox at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080912135907.6880.fche@redhat.com \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).