From: Richard Henderson <richard.henderson@linaro.org>
To: Gustavo Romero <gustavo.romero@linaro.org>, qemu-devel@nongnu.org
Cc: alex.bennee@linaro.org, peter.maydell@linaro.org,
laurent@vivier.eu, philmd@linaro.org
Subject: Re: [PATCH v3 4/5] gdbstub: Add Xfer:siginfo:read stub
Date: Mon, 11 Mar 2024 07:21:06 -1000 [thread overview]
Message-ID: <9c4e69ce-ec08-40cf-877d-bf4f346f4da7@linaro.org> (raw)
In-Reply-To: <20240309030901.1726211-5-gustavo.romero@linaro.org>
On 3/8/24 17:09, Gustavo Romero wrote:
> Add stub to handle Xfer:siginfo:read packet query that requests the
> machine's siginfo data.
>
> This is used when GDB user executes 'print $_siginfo' and when the
> machine stops due to a signal, for instance, on SIGSEGV. The information
> in siginfo allows GDB to determiner further details on the signal, like
> the fault address/insn when the SIGSEGV is caught.
>
> Signed-off-by: Gustavo Romero<gustavo.romero@linaro.org>
> ---
> gdbstub/gdbstub.c | 8 ++++++++
> gdbstub/internals.h | 1 +
> gdbstub/user.c | 23 +++++++++++++++++++++++
> 3 files changed, 32 insertions(+)
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
next prev parent reply other threads:[~2024-03-11 17:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-09 3:08 [PATCH v3 0/5] Add stub to handle Xfer:siginfo:read query Gustavo Romero
2024-03-09 3:08 ` [PATCH v3 1/5] gdbstub: Rename back gdb_handlesig Gustavo Romero
2024-03-09 3:08 ` [PATCH v3 2/5] linux-user: Move tswap_siginfo out of target code Gustavo Romero
2024-03-09 3:08 ` [PATCH v3 3/5] gdbstub: Save target's siginfo Gustavo Romero
2024-03-11 17:20 ` Richard Henderson
2024-03-09 3:09 ` [PATCH v3 4/5] gdbstub: Add Xfer:siginfo:read stub Gustavo Romero
2024-03-11 17:21 ` Richard Henderson [this message]
2024-03-09 3:09 ` [PATCH v3 5/5] tests/tcg: Add multiarch test for " Gustavo Romero
2024-03-11 15:45 ` [PATCH v3 0/5] Add stub to handle Xfer:siginfo:read query 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=9c4e69ce-ec08-40cf-877d-bf4f346f4da7@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=gustavo.romero@linaro.org \
--cc=laurent@vivier.eu \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.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).