From: "mjw at fedoraproject dot org" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug uprobes/18171] setjmp/longjmp clashing with u[ret]probes, causing SIGSEGV or SIGILL
Date: Wed, 11 Oct 2017 10:49:00 -0000 [thread overview]
Message-ID: <bug-18171-6586-TPbCsgvXok@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18171-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18171
Mark Wielaard <mjw at fedoraproject dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|mjw at fedoraproject dot org |
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2017-10-11 10:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-28 0:27 [Bug uprobes/18171] New: setjmp/longjmp clashing with uprobes, " fche at redhat dot com
2015-03-28 0:31 ` [Bug uprobes/18171] setjmp/longjmp clashing with u[ret]probes, " fche at redhat dot com
2015-03-30 14:17 ` mcermak at redhat dot com
2015-04-09 21:26 ` mjw at redhat dot com
2015-05-22 20:20 ` fche at redhat dot com
2017-10-11 10:44 ` mark at klomp dot org
2017-10-11 10:49 ` mjw at fedoraproject dot org [this message]
2018-10-18 18:39 ` 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-18171-6586-TPbCsgvXok@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).