From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug dyninst/24884] stapdyn crashes with a segmentation fault
Date: Fri, 23 Aug 2019 22:21:00 -0000 [thread overview]
Message-ID: <bug-24884-6586-V3M5dyA8SJ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24884-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24884
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fche at redhat dot com
--- Comment #1 from Frank Ch. Eigler <fche at redhat dot com> ---
Hi, Avi, sorry for not noticing this earlier. Some questions to assist in the
local reproduction of this problem:
- arch: x86-64?
- same script works in lkm (non-dyninst) mode?
- tried stap -p4 --dyninst FOO.stp ; gdb -args stapbpf FOO.so
so as to get a gdb backtrace at the crash site?
- what level of traffic is the httpd process absorbing during this time?
(thus: how much thread / child-process changes?)
- tried targeting a program other than this httpd?
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2019-08-23 22: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 ` fche at redhat dot com [this message]
2019-11-12 13:08 ` [Bug dyninst/24884] " avi@cloudius-systems.com
2019-11-12 13:11 ` avi@cloudius-systems.com
2019-11-12 13:21 ` avi@cloudius-systems.com
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-V3M5dyA8SJ@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).