From: "jistone at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/14490] New: Enable stapdyn in multiarch environments
Date: Sat, 18 Aug 2012 01:46:00 -0000 [thread overview]
Message-ID: <bug-14490-6586@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=14490
Bug #: 14490
Summary: Enable stapdyn in multiarch environments
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
AssignedTo: systemtap@sourceware.org
ReportedBy: jistone@redhat.com
Blocks: 14178
Classification: Unclassified
Right now, stapdyn and Dyninst itself are not well equipped to deal with
multiarch environments. For one, Dyninst uses a single DYNINSTAPI_RT_LIB
environment variable, so it's not possible to set that differently for separate
target processes. Then stap is currently only generating a native shared
library, but it might need to compile with flags like -m32 to be loaded in the
target. And further, if PR14489 does have stapdyn dlopen the library, that
requires stapdyn to match architectures too.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2012-08-18 1:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-18 1:46 jistone at redhat dot com [this message]
2012-09-07 19:37 ` [Bug dyninst/14490] " jistone at redhat dot com
2013-02-13 3:07 ` fche at redhat dot com
2013-06-07 19:55 ` dsmith at redhat dot com
2013-06-07 20:21 ` jistone at redhat dot com
2013-06-10 14:22 ` dsmith at redhat dot com
2013-06-10 18:05 ` jistone at redhat dot com
2013-06-27 21:10 ` dsmith at redhat dot com
2013-06-27 21:32 ` jistone 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-14490-6586@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).