From: "v.ondruch+sourceware-bz at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/10485] auto-path tapset support for process.* probes
Date: Tue, 18 Dec 2012 12:56:00 -0000 [thread overview]
Message-ID: <bug-10485-6586-e4xMBFzJV8@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-10485-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=10485
--- Comment #8 from Vít Ondruch <v.ondruch+sourceware-bz at gmail dot com> 2012-12-18 12:56:37 UTC ---
(In reply to comment #7)
> (In reply to comment #6)
> > I am not even sure if SystemTap can handle libruby-64.stp and libruby-32.stp
> > files both present in tapset directory, both contains the same probe
> > definitions and differs just by process path.
>
> That should work fine. It will simultaneously probe both variants.
Thank you. Will sleep better now :)
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2012-12-18 12:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10485-6586@http.sourceware.org/bugzilla/>
2012-12-18 12:35 ` mjw at redhat dot com
2012-12-18 12:56 ` v.ondruch+sourceware-bz at gmail dot com [this message]
2012-12-20 13:57 ` v.ondruch+sourceware-bz at gmail dot com
2016-06-16 20:24 ` fche at redhat dot com
2016-08-03 18:16 ` flu at redhat dot com
2009-08-05 17:12 [Bug translator/10485] New: " fche at redhat dot com
2009-08-06 9:27 ` [Bug translator/10485] " mjw at redhat dot com
2009-08-06 14:57 ` fche at redhat dot com
2009-08-07 9:20 ` mjw at redhat dot com
2009-08-24 20:59 ` mjw 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-10485-6586-e4xMBFzJV8@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).