From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug dyninst/15724] stapdyn looking for libdyninstAPI_RT.a
Date: Wed, 10 Jul 2013 15:17:00 -0000 [thread overview]
Message-ID: <bug-15724-6586-9w4wZwu942@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15724-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=15724
--- Comment #1 from David Smith <dsmith at redhat dot com> ---
Here's some additional information.
The error messages starting with '--SERIOUS--' and '--FATAL--' are coming from
dyninst instelf, not from stapdyn. Specifically the messages are coming from
the call to patch.processCreate() in mutator::create_process().
It also doesn't seem to matter if you specify the path to the dyninst RT
library (instead of letting stapdyn guess it):
====
DYNINSTAPI_RT_LIB=/usr/lib64/dyninst/libdyninstAPI_RT.so stapdyn -v
/home/dsmith/.systemtap/cache/55/stap_550473d97fe423f6c58bcbdf4e19de73_1121.so
-c 'ldconfig --help'
--SERIOUS-- #101: Runtime library /usr/lib64/dyninst/libdyninstAPI_RT.a does
not exist or cannot be accessed!
--FATAL-- #68: Dyninst was unable to create the specified process
--FATAL-- #68: create process failed bootstrap
stapdyn: ERROR: Couldn't create the target process
====
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2013-07-10 15:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 14:46 [Bug dyninst/15724] New: " dsmith at redhat dot com
2013-07-10 15:17 ` dsmith at redhat dot com [this message]
2017-05-16 18:20 ` [Bug dyninst/15724] " scox at redhat dot com
2017-05-16 18:22 ` scox at redhat dot com
2020-12-11 19:58 ` scox at redhat dot com
2021-05-17 15:48 ` 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=bug-15724-6586-9w4wZwu942@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).