public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
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 20:23:00 -0000	[thread overview]
Message-ID: <bug-20264-6586-Gkglk8CQGR@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 #3 from Frank Ch. Eigler <fche at redhat dot com> ---
(In reply to Philip Withnall from comment #2)
> A related problem is that if I have a custom (hacked up) copy of a library
> (for example, which I'm testing in a process by loading with LD_PRELOAD from
> $HOME), the .stp file for it will never be found. If the hacked up library
> contains new probe points, they can't be used.

It can.  For such cases, you could put your tapset.stp file anywhere you like,
and add its directory to stap's search path with -I.  Your .stp file can
contain the full path name of your preloaded .so in its probe alias.


> I think a nice solution would be if bug #20203 were fixed first, then
> systemtap can be changed to look in the 'systemtap' subdirectory next to
> each library for its .stp files.

That wouldn't work too well, in that enumration and parsing of all .stp files
occurs earlier than analysis of the probe points listed in those .stp files.

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2016-06-16 20:23 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 [this message]
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
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-Gkglk8CQGR@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).