The traditional method is to restore the original instruction replaced by
the breakpoint in text, single-step over that instruction, then restore the
breakpoint in text, then continue. That method requires all-stop so that
while you are stepping the thread that just hit the breakpoint, you can't
On 09/14, Oleg Nesterov wrote:
On 09/13, Roland McGrath wrote:
Locks just between the tracer and ptrace_report_signal are not bad.
OK, but let me think a bit more. I'd really like to avoid adding the
new lock to avoid the very unlikely race with the exiting tracer.
Oh, please take a look
