From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug kprobes/23260] SystemTap usage appears to adversely affect GDB breakpoint functionality
Date: Wed, 25 Jul 2018 20:50:00 -0000 [thread overview]
Message-ID: <bug-23260-6586-kE8DRxZCzH@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23260-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23260
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-07-25
CC| |dsmith at redhat dot com
Ever confirmed|0 |1
--- Comment #5 from Frank Ch. Eigler <fche at redhat dot com> ---
Was able to reproduce a close variant of this here on fedora27 x86-64 (stap
3.3, kernel 4.16.13). What may be going on here is that when systemtap runs
with a designated target process, it may stop & resume it briefly, to make sure
it can emplace any relevant uprobes and properly enumerate all its threads. It
could be that this logic fails to interoperate properly with a process already
stuck in a ptrace stop (T state).
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2018-07-25 20:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 18:06 [Bug kprobes/23260] New: " awillia2 at sourcefire dot com
2018-06-05 18:08 ` [Bug kprobes/23260] " awillia2 at sourcefire dot com
2018-06-06 17:58 ` fche at redhat dot com
2018-06-08 22:01 ` awillia2 at sourcefire dot com
2018-07-19 15:59 ` awillia2 at sourcefire dot com
2018-07-25 20:50 ` fche at redhat dot com [this message]
2020-02-19 21:10 ` fche at redhat dot com
2020-07-09 18:34 ` amerey 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-23260-6586-kE8DRxZCzH@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).