From: "scox at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug dyninst/15724] stapdyn looking for libdyninstAPI_RT.a
Date: Fri, 11 Dec 2020 19:58:50 +0000 [thread overview]
Message-ID: <bug-15724-6586-pB094kVc46@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15724-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=15724
Stan Cox <scox at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #4 from Stan Cox <scox at redhat dot com> ---
First case now works with dyninst-10
% stap --runtime=dyninst -e 'probe process.function("main") { println("hi from
dyninst!") }' -c 'ls'
...
hi from dyninst!
...
The second case fails to insert the probe:
% stap --dyninst -e 'probe process.function("main") { println("hi from
dyninst!") }' -c 'ldconfig --help'
stapdyn:
/work/scox/dyn/fed-release/rawhide/dyninst-10.2.1-1/BUILD/dyninst-10.2.1/dyninst-10.2.1/common/src/addrtranslate-linux.C:266:
Dyninst::LoadedLib* Dyninst::AddressTranslateSysV::getAOut(): Assertion
`phdr_vaddr != (Address) -1' failed.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2020-12-11 19:58 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 ` [Bug dyninst/15724] " dsmith at redhat dot com
2017-05-16 18:20 ` 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 [this message]
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-pB094kVc46@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).