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: Sat, 06 Apr 2019 01:01:00 -0000 [thread overview]
Message-ID: <bug-23513-6586-v529RnJis5@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23513-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23513
--- Comment #4 from Stan Cox <scox at redhat dot com> ---
Running with DYNINST_DEBUG_STARTUP=1
it seems the problem is dyninst fails to parse the stap so (not sure why) and
intentionally terminates the process.
[140306531820032]image.C[1461]: opening file
/tmp/stapSmTcdi/stap_2ecef162cf9d3c769f9c52398beab57b_1423.so
[140306531820032]image.C[1226]: created image
[140306531820032]image.C[1229]: processing shared object
[140306531820032]image.C[1247]: error in processing, deleting image and
returning
[140306531820032]mapped_object.C[157]: failed to parseImage
[140306531820032]dynProcess.C[618]: failed to create mapped object for library
/tmp/stapSmTcdi/stap_2ecef162cf9d3c769f9c52398beab57b_1423.so
[140306531820032]dynProcess.C[361]: bootstrap failed while creating mapped
objects
Failed to bootstrap process 9255: terminating...
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2019-04-06 1:01 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 [this message]
2019-04-10 12:42 ` scox at redhat dot com
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-v529RnJis5@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).