This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug kprobes/23260] SystemTap usage appears to adversely affect GDB breakpoint functionality


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.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]