From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/20264] Load tapsets from $libdir for multiarch
Date: Thu, 16 Jun 2016 21:04:00 -0000 [thread overview]
Message-ID: <bug-20264-6586-SulnfNInkJ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-20264-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20264
--- Comment #5 from Frank Ch. Eigler <fche at redhat dot com> ---
> Hmm. So the problem is that .stp files need to be loaded before the .so
> files are looked at. For user-space probing, would it be possible to
> enumerate the libraries in a process' address space, work out the library
> paths, append 'systemtap' to all of them, then search for .stp files in
> those directories?
That could be implementable - though which process? stap -x $PID is apprx.
the only way to refer to a single existing process.
You might find bug #10485 a more general solution. It relies on placement of
tapset .stp files under a searchably small hierarchy under an existing tapset/
directory.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2016-06-16 21:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 17:16 [Bug tapsets/20264] New: " bugzilla at tecnocode dot co.uk
2016-06-16 17:35 ` [Bug tapsets/20264] " fche at redhat dot com
2016-06-16 20:14 ` bugzilla at tecnocode dot co.uk
2016-06-16 20:15 ` bugzilla at tecnocode dot co.uk
2016-06-16 20:23 ` fche at redhat dot com
2016-06-16 20:24 ` fche at redhat dot com
2016-06-16 20:49 ` bugzilla at tecnocode dot co.uk
2016-06-16 21:04 ` fche at redhat dot com [this message]
2019-05-21 17:43 ` fche 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=bug-20264-6586-SulnfNInkJ@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/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).