From: "avi@cloudius-systems.com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug dyninst/24884] stapdyn crashes with a segmentation fault
Date: Tue, 12 Nov 2019 13:21:00 -0000 [thread overview]
Message-ID: <bug-24884-6586-iFadJ4D0u0@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24884-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24884
--- Comment #4 from Avi Kivity <avi@cloudius-systems.com> ---
And now I get segmentation faults again.
#0 int_process::removeAllBreakpoints (this=0x55bf9c39eab8) at
/usr/include/c++/9/bits/stl_tree.h:208
#1 0x00007f0c1737589f in linux_process::preTerminate (this=0x55bf9c39e820) at
/usr/src/debug/dyninst-10.0.0-7.fc30.x86_64/dyninst-10.0.0/proccontrol/src/linux.C:1740
#2 0x00007f0c1733a4d1 in Dyninst::ProcControlAPI::ProcessSet::terminate
(this=0x55bfb12f09e0) at
/usr/src/debug/dyninst-10.0.0-7.fc30.x86_64/dyninst-10.0.0/proccontrol/src/procset.C:1644
#3 0x00007f0c172d95db in Dyninst::ProcControlAPI::Process::terminate
(this=<optimized out>) at /usr/include/boost/smart_ptr/shared_ptr.hpp:732
#4 0x00007f0c17da7ab5 in PCProcess::terminateProcess (this=0x55bfa0f37cb0) at
/usr/include/boost/smart_ptr/shared_ptr.hpp:732
#5 PCProcess::terminateProcess (this=0x55bfa0f37cb0) at
/usr/src/debug/dyninst-10.0.0-7.fc30.x86_64/dyninst-10.0.0/dyninstAPI/src/dynProcess.C:1027
#6 0x00007f0c17db377c in PCProcess::attachProcess (progpath=..., pid=16581,
analysisMode=BPatch_normalMode) at
/usr/src/debug/dyninst-10.0.0-7.fc30.x86_64/dyninst-10.0.0/dyninstAPI/src/dynProcess.C:162
#7 0x00007f0c17cf269a in BPatch_process::BPatch_process(char const*, int,
BPatch_hybridMode) () at
/usr/src/debug/dyninst-10.0.0-7.fc30.x86_64/dyninst-10.0.0/dyninstAPI/src/BPatch_process.C:328
#8 0x00007f0c17ccf027 in BPatch::processAttach (this=<optimized out>,
path=0x0, pid=16581, mode=BPatch_normalMode) at
/usr/src/debug/dyninst-10.0.0-7.fc30.x86_64/dyninst-10.0.0/dyninstAPI/src/BPatch.C:1260
#9 0x000055bf9abb4519 in ?? ()
#10 0x000055bf9c362440 in ?? ()
#11 0x00007ffd51a63ec0 in ?? ()
#12 0x00000000000040c5 in probe_13397 ()
#13 0x0000000000000000 in ?? ()
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2019-11-12 13:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 16:43 [Bug dyninst/24884] New: " avi@cloudius-systems.com
2019-08-23 22:21 ` [Bug dyninst/24884] " fche at redhat dot com
2019-11-12 13:08 ` avi@cloudius-systems.com
2019-11-12 13:11 ` avi@cloudius-systems.com
2019-11-12 13:21 ` avi@cloudius-systems.com [this message]
2019-11-12 13:25 ` avi@cloudius-systems.com
2019-11-12 13:38 ` avi@cloudius-systems.com
2019-11-23 1:26 ` fche at redhat dot com
2019-11-24 8:57 ` avi@cloudius-systems.com
2019-12-04 10:32 ` avi@cloudius-systems.com
2019-12-09 22:04 ` fche 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-24884-6586-iFadJ4D0u0@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).