public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "leisurelysw24 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug uprobes/24117] System crashes when probing a shared library
Date: Thu, 31 Jan 2019 04:35:00 -0000	[thread overview]
Message-ID: <bug-24117-6586-nTZvICdFa2@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24117-6586@http.sourceware.org/bugzilla/>

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

--- Comment #2 from Jerry Lee <leisurelysw24 at gmail dot com> ---
Created attachment 11579
  --> https://sourceware.org/bugzilla/attachment.cgi?id=11579&action=edit
output for stap-report

Hi,

It's really exciting to hear from you :D.  The outcome of stap-report is
attached.

(In reply to Serhei Makarov from comment #1)
> Hello,
> 
> I have the indicated kernel version on a Fedora 28 system, but not
> libuLinux_hal.so. Trying to reproduce the problem with other shared
> libraries (e.g. /lib/libc.so.6) on did not yield a crash. Is there a
> distro/package/tarball I can install to get libuLinux_hal.so?

Sorry, libuLinux_hal.so is a customized library which is not available on any
distro/package/tarabll.  So, instead, I tried to probe the libc.so.6 as below
but unfortunately got the same result.

#!/usr/bin/env stap

probe process("/lib/libc.so.6").function("fork")
{
        printf("fork called\n")
}

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

  parent reply	other threads:[~2019-01-31  4:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-22  9:51 [Bug uprobes/24117] New: " leisurelysw24 at gmail dot com
2019-01-30 22:06 ` [Bug uprobes/24117] " me at serhei dot io
2019-01-31  4:35 ` leisurelysw24 at gmail dot com [this message]
2019-01-31 20:04 ` me at serhei dot io
2019-02-01  2:06 ` leisurelysw24 at gmail dot com
2019-07-29  1:54 ` leisurelysw24 at gmail 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-24117-6586-nTZvICdFa2@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).