public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "avi@cloudius-systems.com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug dyninst/24884] New: stapdyn crashes with a segmentation fault
Date: Mon, 05 Aug 2019 16:43:00 -0000	[thread overview]
Message-ID: <bug-24884-6586@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=24884

            Bug ID: 24884
           Summary: stapdyn crashes with a segmentation fault
           Product: systemtap
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: dyninst
          Assignee: systemtap at sourceware dot org
          Reporter: avi@cloudius-systems.com
  Target Milestone: ---

Trying the following script:


#!/usr/bin/stap

# usage: task-histogram.stap process_name

global hist

probe process.mark("reactor_run_tasks_single_start") {
    ++hist[tid(), $arg1]
}

probe end {
    foreach ([tid, addr] in hist) {
        printf("%10d %8d 0x%x\n", hist[tid, addr], tid, addr)
    }
}


(trying to collect a histogram of tasks)

With this command line:

    stap --dyninst -x $(pgrep -x httpd) ./debug/task-histogram.stap

Crashes with

WARNING: /usr/bin/stapdyn exited with signal: 11 (Segmentation fault)


systemtap-4.1-1.fc30.x86_64

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

             reply	other threads:[~2019-08-05 16:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-05 16:43 avi@cloudius-systems.com [this message]
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
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@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).