public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug dyninst/15724] New: stapdyn looking for libdyninstAPI_RT.a
Date: Wed, 10 Jul 2013 14:46:00 -0000	[thread overview]
Message-ID: <bug-15724-6586@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=15724

            Bug ID: 15724
           Summary: stapdyn looking for libdyninstAPI_RT.a
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: dyninst
          Assignee: systemtap at sourceware dot org
          Reporter: dsmith at redhat dot com

Here's a fairly normal stapdyn command:

====
# stap -v --runtime=dyninst -e 'probe process.function("main") { println("hi
from dyninst!") }' -c 'ls'
Pass 1: parsed user script and 32 library script(s) using
191164virt/9356res/2996shr/6204data kb, in 10usr/10sys/14real ms.
Pass 2: analyzed script: 1 probe(s), 0 function(s), 0 embed(s), 0 global(s)
using 193172virt/11740res/3860shr/7604data kb, in 0usr/40sys/148real ms.
Pass 3: using cached
/home/dsmith/.systemtap/cache/d9/stap_d901300581675708014e456630b46d12_1056.c
Pass 4: using cached
/home/dsmith/.systemtap/cache/d9/stap_d901300581675708014e456630b46d12_1056.so
Pass 5: starting run.
stap.txt
Pass 5: run completed in 2500usr/390sys/3184real ms.
====

Notice the probe didn't hit (perhaps "main" is too early in the process'
life?), but that isn't the problem here. Now I run the same command, using
ldconfig instead of ls:

====
# stap -v --runtime=dyninst -e 'probe process.function("main") { println("hi
from dyninst!") }' -c 'ldconfig --help'
Pass 1: parsed user script and 32 library script(s) using
191164virt/8824res/2464shr/6204data kb, in 20usr/10sys/40real ms.
Pass 2: analyzed script: 1 probe(s), 0 function(s), 0 embed(s), 0 global(s)
using 197384virt/12652res/4680shr/8064data kb, in 30usr/30sys/126real ms.
Pass 3: using cached
/home/dsmith/.systemtap/cache/55/stap_550473d97fe423f6c58bcbdf4e19de73_1121.c
Pass 4: using cached
/home/dsmith/.systemtap/cache/55/stap_550473d97fe423f6c58bcbdf4e19de73_1121.so
Pass 5: starting run.
--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
WARNING: /usr/local/bin/stapdyn exited with status: 1
Pass 5: run completed in 20usr/150sys/1058real ms.
Pass 5: run failed.  [man error::pass5] 
====

For some reason stapdyn is looking for libdyninstAPI_RT.a instead of
libdyninstAPI_RT.so. Very odd.

This is on rawhide - 3.11.0-0.rc0.git2.1.fc20.x86_64.

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

             reply	other threads:[~2013-07-10 14:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-10 14:46 dsmith at redhat dot com [this message]
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
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@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).