From: "me at serhei dot io" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug uprobes/24117] System crashes when probing a shared library
Date: Thu, 31 Jan 2019 20:04:00 -0000 [thread overview]
Message-ID: <bug-24117-6586-7Q0ZCldeFt@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 #3 from Serhei Makarov <me at serhei dot io> ---
I took a look at the stap-report but the section containing kernel config did
not generate properly. Can you please also send your
/lib/modules/4.14.24/build/.config?
> So, instead, I tried to probe the libc.so.6 as below but unfortunately got the same result.
That's helpful to know, since it means your custom library isn't needed to
reproduce. Thus far, I have not seen a kernel crash with the example you sent.
My guess is that the kernel you are using has a different CONFIG from mine, or
even some custom patches.
However, I do see a segmentation fault when probing a 32-bit program on my
64-bit system (since /lib/libc.so.6 on my system is 32-bit), which is
definitely a bug (though not the same as the result you're seeing). Is the
program/library you are probing 32-bit on a 64-bit system as well?
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2019-01-31 20:04 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
2019-01-31 20:04 ` me at serhei dot io [this message]
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-7Q0ZCldeFt@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).