* [Bug 217001] New: Undocumented behavior of ptrace(2) when a seized process gets SIGCONT
@ 2023-02-04 8:15 bugzilla-daemon
2023-05-19 12:12 ` [Bug 217001] " bugzilla-daemon
2023-05-19 12:12 ` bugzilla-daemon
0 siblings, 2 replies; 3+ messages in thread
From: bugzilla-daemon @ 2023-02-04 8:15 UTC (permalink / raw)
To: linux-man
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: documentation_man-pages@kernel-bugs.osdl.org
Reporter: takahashi.shuhei@gmail.com
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:
> PTRACE_EVENT_STOP
> Stop induced by PTRACE_INTERRUPT command, or group-stop,
> or initial ptrace-stop when a new child is attached (only
> if attached using PTRACE_SEIZE).
Here's code to reproduce the behavior (in Rust):
https://github.com/nix-rust/nix/pull/1996/files#diff-65efa0db9bf3f9cbccfee8c987cb6c98ecf77576e0b46a87cab7ec4cfcbff172R324
I saw this behavior is explained in the following stackoverflow entry.
https://stackoverflow.com/a/49468347
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug 217001] Undocumented behavior of ptrace(2) when a seized process gets SIGCONT
2023-02-04 8:15 [Bug 217001] New: Undocumented behavior of ptrace(2) when a seized process gets SIGCONT bugzilla-daemon
@ 2023-05-19 12:12 ` bugzilla-daemon
2023-05-19 12:12 ` bugzilla-daemon
1 sibling, 0 replies; 3+ messages in thread
From: bugzilla-daemon @ 2023-05-19 12:12 UTC (permalink / raw)
To: linux-man
https://bugzilla.kernel.org/show_bug.cgi?id=217001
--- Comment #1 from Alejandro Colomar (alx@kernel.org) ---
Would you please send a patch according to the ./CONTRIBUTING file in the
repo?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug 217001] Undocumented behavior of ptrace(2) when a seized process gets SIGCONT
2023-02-04 8:15 [Bug 217001] New: Undocumented behavior of ptrace(2) when a seized process gets SIGCONT bugzilla-daemon
2023-05-19 12:12 ` [Bug 217001] " bugzilla-daemon
@ 2023-05-19 12:12 ` bugzilla-daemon
1 sibling, 0 replies; 3+ messages in thread
From: bugzilla-daemon @ 2023-05-19 12:12 UTC (permalink / raw)
To: linux-man
https://bugzilla.kernel.org/show_bug.cgi?id=217001
Alejandro Colomar (alx@kernel.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-05-19 12:12 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-02-04 8:15 [Bug 217001] New: Undocumented behavior of ptrace(2) when a seized process gets SIGCONT bugzilla-daemon
2023-05-19 12:12 ` [Bug 217001] " bugzilla-daemon
2023-05-19 12:12 ` bugzilla-daemon
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 NNTP newsgroup(s).