From: Alejandro Colomar <alx.manpages@gmail.com>
To: "Φώτης Βαλασιάδης" <fvalasiad@gmail.com>,
"Dmitry V. Levin" <ldv@strace.io>
Cc: linux-man@vger.kernel.org, mtk.manpages@gmail.com,
lineprinter0@gmail.com
Subject: Re: [PATCH] ptrace.2: Add details about usage of PTRACE_GET_SYSCALL_INFO
Date: Mon, 27 Feb 2023 19:48:05 +0100 [thread overview]
Message-ID: <9f4aaf34-66cc-554f-d45f-73f0bb9b4a94@gmail.com> (raw)
In-Reply-To: <b57591a9-5ba1-5192-f376-f2de812a9086@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 807 bytes --]
Hi Φώτης,
On 2/27/23 18:27, Φώτης Βαλασιάδης wrote:
>>>
> So with Dmitry we agreed on:
>
> 1.
>
> Came upon this after writing a test program using PTRACE_GET_SYSCALL_INFO.
>
> 2.
>
> In the code it can be seen that in case of system call entry or
> exit stops, the union is filled if and only if the signal matches
> "SIGTRAP | 0x80", a signal which is sent if the PTRACE_O_TRACESYSGOOD
> option is set. You can read about that in the PTRACE_O_TRACESYSGOOD
> section of ptrace(2)'s manual.
>
> Replace these and we are set!
Would you mind sending the patch again with that text? :)
Thanks!
Alex
>
> -- fvalasiad --
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-02-27 18:48 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-25 10:56 [PATCH] ptrace.2: Add details about usage of PTRACE_GET_SYSCALL_INFO Fotios Valasiadis
2023-02-26 21:58 ` Alejandro Colomar
2023-02-26 22:03 ` Dmitry V . Levin
2023-02-26 22:05 ` Alejandro Colomar
2023-02-26 22:14 ` Φώτης Βαλασιάδης
2023-02-26 22:42 ` Alejandro Colomar
2023-02-26 23:30 ` Φώτης Βαλασιάδης
2023-02-26 23:22 ` Fotios Valasiadis
2023-02-27 0:19 ` Alejandro Colomar
2023-02-27 0:41 ` Φώτης Βαλασιάδης
2023-02-27 13:28 ` Alejandro Colomar
2023-02-27 15:33 ` Dmitry V. Levin
2023-02-27 15:35 ` Alejandro Colomar
[not found] ` <b57591a9-5ba1-5192-f376-f2de812a9086@gmail.com>
2023-02-27 17:30 ` Fwd: " Φώτης Βαλασιάδης
2023-02-27 18:48 ` Alejandro Colomar [this message]
2023-02-27 19:17 ` Fotios Valasiadis
2023-02-27 19:19 ` Φώτης Βαλασιάδης
2023-03-01 19:28 ` Φώτης Βαλασιάδης
2023-03-01 21:00 ` Alejandro Colomar
-- strict thread matches above, loose matches on Subject: below --
2023-02-25 2:42 Fotios Valasiadis
2023-02-25 10:10 ` Dmitry V . Levin
2023-02-25 10:33 ` Φώτης Βαλασιάδης
2023-02-25 10:42 ` Dmitry V . Levin
2023-02-24 16:31 Fotios Valasiadis
2023-02-24 18:53 ` Dmitry V. Levin
2023-02-24 19:11 ` Φώτης Βαλασιάδης
2023-02-24 22:05 ` Dmitry V. Levin
2023-02-24 23:05 ` Φώτης Βαλασιάδης
2023-02-24 23:31 ` Dmitry V. Levin
2023-02-24 23:43 ` Φώτης Βαλασιάδης
2023-02-25 0:08 ` Dmitry V. Levin
2023-02-25 1:21 ` Alex Colomar
2023-02-25 9:39 ` Dmitry V. Levin
2023-02-25 1:18 ` Alex Colomar
2023-02-25 1:36 ` Φώτης Βαλασιάδης
2023-02-25 2:07 ` Nate Eldredge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9f4aaf34-66cc-554f-d45f-73f0bb9b4a94@gmail.com \
--to=alx.manpages@gmail.com \
--cc=fvalasiad@gmail.com \
--cc=ldv@strace.io \
--cc=lineprinter0@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox