Better?
diff --git a/man2/ptrace.2 b/man2/ptrace.2
index 55d9fd36d..ad0543b0b 100644
--- a/man2/ptrace.2
+++ b/man2/ptrace.2
@@ -1111,6 +1111,15 @@ stop.
.B PTRACE_SYSCALL_INFO_NONE
No component of the union contains relevant information.
.RE
+.IP
+Note that in case of
+syscall entry or exit stops, the data returned by
+.B PTRACE_GET_SYSCALL_INFO
+is limited to type
+.B PTRACE_SYSCALL_INFO_NONE
+unless
+.B PTRACE_O_TRACESYSGOOD
+option is set before the corresponding ptrace stop has occurred.
.\"
.SS Death under ptrace
When a (possibly multithreaded) process receives a killing signal
On 25/2/23 01:31, Dmitry V. Levin wrote:
On Sat, Feb 25, 2023 at 01:05:24AM +0200, Φώτης Βαλασιάδης wrote:
So, what about this?
diff --git a/man2/ptrace.2 b/man2/ptrace.2
index 55d9fd36d..e5f49c289 100644
--- a/man2/ptrace.2
+++ b/man2/ptrace.2
@@ -1111,6 +1111,16 @@ stop.
.B PTRACE_SYSCALL_INFO_NONE
No component of the union contains relevant information.
.RE
+.IP
+Note that in case of
+.B PTRACE_SYSCALL
+syscall entry or exit stops, the data returned by
I'm not sure about mentioning PTRACE_SYSCALL in this context as it's not
the only way to have the tracee stopped at a syscall stop.
+.B PTRACE_GET_SYSCALL_INFO
+is limited to type
+.B PTRACE_SYSCALL_INFO_NONE
+unless
+.B PTRACE_O_TRACESYSGOOD
+option is set before the corresponding ptrace stop has occurred.
.\"
.SS Death under ptrace
When a (possibly multithreaded) process receives a killing signal
