New: Undocumented behavior of ptrace(2) when a seized process gets SIGCONT
https://bugzilla.kernel.org/show_bug.cgi?id=217001
Bug ID: 217001
Summary: Undocumented behavior of ptrace(2) when a seized
process gets SIGCONT
Product: Documentation
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P1
Component: man-pages
Assignee: [email protected]
Reporter: [email protected]
Regression: No
When we use ptrace(PTRACE_SEIZE) to attach to a process, sending SIGCONT to the tracee causes the tracer to get notified with PTRACE_EVENT_STOP with SIGTRAP, but this behavior is not documented in the ptrace(2) man page.
The man page says:
Quoted 4 lines
PTRACE_EVENT_STOP
Stop induced byPTRACE_INTERRUPTcommand, or group-stop, or initial ptrace-stop when a new child is attached (only if attached usingPTRACE_SEIZE).
Here's code to reproduce the behavior (in Rust):
I saw this behavior is explained in the following stackoverflow entry.
https://stackoverflow.com/a/49468347
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 217001] Undocumented behavior of ptrace(2) when a seized process gets SIGCONT
https://bugzilla.kernel.org/show_bug.cgi?id=217001
--- Comment #1 from Alejandro Colomar ([email protected]) --- Would you please send a patch according to the ./CONTRIBUTING file in the repo?
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
[Bug 217001] Undocumented behavior of ptrace(2) when a seized process gets SIGCONT
In reply to [email protected]https://bugzilla.kernel.org/show_bug.cgi?id=217001
Alejandro Colomar ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.