From: "scox at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug dyninst/23513] Dyninst runtime kills the target process when attaching to the target process for a second time
Date: Wed, 10 Apr 2019 12:42:00 -0000 [thread overview]
Message-ID: <bug-23513-6586-s2yPnNC1DB@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23513-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23513
Stan Cox <scox at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-04-10
Ever confirmed|0 |1
--- Comment #5 from Stan Cox <scox at redhat dot com> ---
The problem seems intermittant but I do see it and the culprit is that the stap
shared object is not always detached when stapdyn completes. (gdb session
after failing stapdyn)
(gdb) info sharedlibrary
From To Syms Read Shared Object Library
0x00007f3bd7f64670 0x00007f3bd80afc3f Yes (*) /lib64/libc.so.6
0x00007f3bd8139110 0x00007f3bd81582b4 Yes (*) /lib64/ld-linux-x86-64.so.2
0x00007f3bd6eb2320 0x00007f3bd6eb4845 Yes (*)
/usr/lib64/dyninst/libdyninstAPI_RT.so
0x00007f3bd6eab270 0x00007f3bd6eac039 Yes (*) /lib64/libdl.so.2
No
/tmp/stapUaA2KQ/stap_4e52f2023ce6edaabf143f6d5214b684_1361.so
0x00007f3bd8124710 0x00007f3bd8127a80 Yes (*) /lib64/librt.so.1
0x00007f3bd6e60b50 0x00007f3bd6e6f025 Yes (*) /lib64/libpthread.so.0
(*): Shared library is missing debugging information.
So whenever stapdyn subsequently runs, dyninst tries to load that nonexistant
library: /tmp/stapUaA2KQ/stap_4e52f2023ce6edaabf143f6d5214b684_1361.so
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2019-04-10 12:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-11 0:34 [Bug dyninst/23513] New: " agentzh at gmail dot com
2018-08-11 0:39 ` [Bug dyninst/23513] " fche at redhat dot com
2018-08-11 0:46 ` agentzh at gmail dot com
2019-04-05 19:07 ` scox at redhat dot com
2019-04-06 1:01 ` scox at redhat dot com
2019-04-10 12:42 ` scox at redhat dot com [this message]
2019-12-11 16:25 ` avi@cloudius-systems.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-23513-6586-s2yPnNC1DB@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).