From: Ilya Leoshkevich <iii@linux.ibm.com>
To: "Richard Henderson" <richard.henderson@linaro.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"David Hildenbrand" <david@redhat.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-devel@nongnu.org, qemu-arm@nongnu.org,
qemu-s390x@nongnu.org, "Ilya Leoshkevich" <iii@linux.ibm.com>
Subject: [PATCH 0/3] linux-user: Allow gdbstub to ignore page protection
Date: Tue, 9 Jan 2024 00:34:05 +0100 [thread overview]
Message-ID: <20240108233821.201325-1-iii@linux.ibm.com> (raw)
RFC: https://lists.gnu.org/archive/html/qemu-devel/2023-12/msg02044.html
RFC -> v1: Use /proc/self/mem and accept that this will not work
without /proc.
Factor out a couple functions for gdbstub testing.
Add a test.
Hi,
I've noticed that gdbstub behaves differently from gdbserver in that it
doesn't allow reading non-readable pages. This series improves the
situation by using the same mechanism as gdbserver: /proc/self/mem. If
/proc is not mounted, we fall back to the today's implementation.
Best regards,
Ilya
Ilya Leoshkevich (3):
linux-user: Allow gdbstub to ignore page protection
tests/tcg: Factor out gdbstub test functions
tests/tcg: Add the PROT_NONE gdbstub test
cpu-target.c | 55 +++++++++++++-----
tests/guest-debug/run-test.py | 7 ++-
tests/guest-debug/test_gdbstub.py | 56 +++++++++++++++++++
tests/tcg/aarch64/gdbstub/test-sve-ioctl.py | 34 +----------
tests/tcg/aarch64/gdbstub/test-sve.py | 33 +----------
tests/tcg/multiarch/Makefile.target | 9 ++-
tests/tcg/multiarch/gdbstub/interrupt.py | 47 ++--------------
tests/tcg/multiarch/gdbstub/memory.py | 41 +-------------
tests/tcg/multiarch/gdbstub/prot-none.py | 22 ++++++++
tests/tcg/multiarch/gdbstub/registers.py | 41 ++------------
tests/tcg/multiarch/gdbstub/sha1.py | 40 ++-----------
.../multiarch/gdbstub/test-proc-mappings.py | 39 +------------
.../multiarch/gdbstub/test-qxfer-auxv-read.py | 37 +-----------
.../gdbstub/test-thread-breakpoint.py | 37 +-----------
tests/tcg/multiarch/prot-none.c | 38 +++++++++++++
tests/tcg/s390x/gdbstub/test-signals-s390x.py | 42 +-------------
tests/tcg/s390x/gdbstub/test-svc.py | 39 +------------
17 files changed, 204 insertions(+), 413 deletions(-)
create mode 100644 tests/guest-debug/test_gdbstub.py
create mode 100644 tests/tcg/multiarch/gdbstub/prot-none.py
create mode 100644 tests/tcg/multiarch/prot-none.c
--
2.43.0
next reply other threads:[~2024-01-08 23:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 23:34 Ilya Leoshkevich [this message]
2024-01-08 23:34 ` [PATCH 1/3] linux-user: Allow gdbstub to ignore page protection Ilya Leoshkevich
2024-01-09 17:42 ` Richard Henderson
2024-01-09 19:39 ` Ilya Leoshkevich
2024-01-09 21:47 ` Richard Henderson
2024-01-08 23:34 ` [PATCH 2/3] tests/tcg: Factor out gdbstub test functions Ilya Leoshkevich
2024-01-08 23:34 ` [PATCH 3/3] tests/tcg: Add the PROT_NONE gdbstub test Ilya Leoshkevich
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=20240108233821.201325-1-iii@linux.ibm.com \
--to=iii@linux.ibm.com \
--cc=alex.bennee@linaro.org \
--cc=david@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
/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).