From: "fahadaliarshad at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug uprobes/18340] Segmentation fault of probed SSHD program
Date: Wed, 29 Apr 2015 12:09:00 -0000 [thread overview]
Message-ID: <bug-18340-6586-YavCklPPQ9@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18340-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18340
--- Comment #4 from fahadaliarshad at gmail dot com ---
Frank,
Thanks for providing feedback on this.
I was going to build from source a kernel version > 3.13. But before that, I
updated my system (yum update) and kernel version updated from
"3.10.0-123.9.3.el7.x86_64" to the latest version "3.10.0-229.1.2.el7.x86_64"
available by Centos7 repo.
Apparently, this fixed the issue!
I am still not sure what was the root-cause though.
There is no segfault anymore but I do see a "WARNING: function _start return"
as below.
[root@centos7 ~]# stap -v -e 'probe
process("/usr/local/openssh-5.3p1/sbin/sshd").function("*") {printf("[%d]
funcname:%s->\n", gettimeofday_us(), pp())} probe
process("/usr/local/openssh-5.3p1/sbin/sshd").function("*").return
{printf("[%d] funcname:%s<-\n", gettimeofday_us(), pp())}'
Pass 1: parsed user script and 106 library script(s) using
217156virt/34680res/2992shr/32188data kb, in 220usr/60sys/288real ms.
WARNING: function _start return probe is blacklisted: keyword at <input>:1:131
source: probe process("/usr/local/openssh-5.3p1/sbin/sshd").function("*")
{printf("[%d] funcname:%s->\n", gettimeofday_us(), pp())} probe
process("/usr/local/openssh-5.3p1/sbin/sshd").function("*").return
{printf("[%d] funcname:%s<-\n", gettimeofday_us(), pp())}
^
Pass 2: analyzed script: 1982 probe(s), 3 function(s), 1 embed(s), 0 global(s)
using 225440virt/43964res/3732shr/40472data kb, in 180usr/20sys/183real ms.
Pass 3: using cached
/root/.systemtap/cache/a6/stap_a6c26ef9098b1d31ec5d9d07d982715b_652697.c
Pass 4: using cached
/root/.systemtap/cache/a6/stap_a6c26ef9098b1d31ec5d9d07d982715b_652697.ko
Pass 5: starting run.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2015-04-29 12:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 3:16 [Bug translator/18340] New: " fahadaliarshad at gmail dot com
2015-04-28 10:58 ` [Bug uprobes/18340] " fche at redhat dot com
2015-04-28 11:18 ` fahadaliarshad at gmail dot com
2015-04-28 11:29 ` fche at redhat dot com
2015-04-29 12:09 ` fahadaliarshad at gmail dot com [this message]
2015-04-29 12:55 ` 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-18340-6586-YavCklPPQ9@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).