From: "cap at nsc dot liu dot se" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/6880] more syntax for shared library probing
Date: Wed, 20 May 2009 20:30:00 -0000 [thread overview]
Message-ID: <20090520202957.7266.qmail@sourceware.org> (raw)
In-Reply-To: <20080912135907.6880.fche@redhat.com>
------- Additional Comments From cap at nsc dot liu dot se 2009-05-20 20:29 -------
I really like that you're currently able to do:
probe process("/lib/libx.so").function("f")
and by this having a systemwide probe that will catch any task that calls f()
from libx.
If, in the future, this could be improved to:
probe library("libx").function("f")
with the following improvements:
* find libx in the current env. (LD_LIBRARY_PATH, ld.so.conf, etc.)
* work with only the symbol table and not require dwarf
then that would be very nice.
I apologise if this comment was OT, I think/hope it was close enough to be
relevant...
--
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 prev parent reply other threads:[~2009-05-20 20:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 14:00 [Bug translator/6880] New: " fche at redhat dot com
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 [this message]
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=20090520202957.7266.qmail@sourceware.org \
--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).