From: Ilya Leoshkevich <iii@linux.ibm.com>
To: "Alex Bennée" <alex.bennee@linaro.org>,
"Riku Voipio" <riku.voipio@iki.fi>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-devel@nongnu.org, "Ilya Leoshkevich" <iii@linux.ibm.com>
Subject: [PATCH v2 0/2] gdbstub: Implement catching syscalls
Date: Tue, 16 Jan 2024 10:41:52 +0100 [thread overview]
Message-ID: <20240116094411.216665-1-iii@linux.ibm.com> (raw)
Based-on: <20240116003551.75168-1-iii@linux.ibm.com>
([PATCH v3 0/3] linux-user: Allow gdbstub to ignore page protection)
v1: https://lists.gnu.org/archive/html/qemu-devel/2024-01/msg02911.html
v1 -> v2: Avoid touching the system gdbstub.
Advertise QCatchSyscalls+ only on Linux.
Hi,
I noticed that GDB's "catch syscall" does not work with qemu-user.
This series adds the missing bits in [1/2] and a test in [2/2].
I'm basing this on my other series, since it contains useful gdbstub
test refactorings.
Best regards,
Ilya
Ilya Leoshkevich (2):
gdbstub: Implement catching syscalls
tests/tcg: Add the syscall catchpoint gdbstub test
gdbstub/gdbstub.c | 9 ++
gdbstub/internals.h | 2 +
gdbstub/user-target.c | 5 +
gdbstub/user.c | 104 +++++++++++++++++-
include/gdbstub/user.h | 29 ++++-
include/user/syscall-trace.h | 7 +-
tests/tcg/multiarch/Makefile.target | 10 +-
tests/tcg/multiarch/catch-syscalls.c | 51 +++++++++
tests/tcg/multiarch/gdbstub/catch-syscalls.py | 52 +++++++++
9 files changed, 263 insertions(+), 6 deletions(-)
create mode 100644 tests/tcg/multiarch/catch-syscalls.c
create mode 100644 tests/tcg/multiarch/gdbstub/catch-syscalls.py
--
2.43.0
next reply other threads:[~2024-01-16 9:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 9:41 Ilya Leoshkevich [this message]
2024-01-16 9:41 ` [PATCH v2 1/2] gdbstub: Implement catching syscalls Ilya Leoshkevich
2024-02-01 17:15 ` Alex Bennée
2024-02-02 14:30 ` Ilya Leoshkevich
2024-01-16 9:41 ` [PATCH v2 2/2] tests/tcg: Add the syscall catchpoint gdbstub test Ilya Leoshkevich
2024-02-01 17:16 ` Alex Bennée
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=20240116094411.216665-1-iii@linux.ibm.com \
--to=iii@linux.ibm.com \
--cc=alex.bennee@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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;
as well as URLs for NNTP newsgroup(s).