From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug uprobes/18340] Segmentation fault of probed SSHD program
Date: Tue, 28 Apr 2015 11:29:00 -0000 [thread overview]
Message-ID: <bug-18340-6586-FMyce2RDWe@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 #3 from Frank Ch. Eigler <fche at redhat dot com> ---
> Removing the .return probe did not help and I am observing the same behavior
> (Segmentation fault).
OK. A number of kernel uprobe bugs were fixed after 3.13; would you be able to
test with a more recent version?
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2015-04-28 11:29 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 [this message]
2015-04-29 12:09 ` fahadaliarshad at gmail dot com
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-FMyce2RDWe@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).