From: Richard Henderson <richard.henderson@linaro.org>
To: Helge Deller <deller@gmx.de>, qemu-devel@nongnu.org
Subject: Re: [PATCH] Fix signal handler to detect crashes in qemu-linux-user
Date: Sat, 12 Aug 2023 10:33:11 -0700 [thread overview]
Message-ID: <56908f79-c883-0d83-c990-e7a86714b6da@linaro.org> (raw)
In-Reply-To: <20230812164314.352131-1-deller@gmx.de>
On 8/12/23 09:43, Helge Deller wrote:
> +/* _init and _fini are provided by the linker */
> +extern char _init;
> +extern char _fini;
> +
> static void host_signal_handler(int host_sig, siginfo_t *info, void *puc)
> {
> CPUArchState *env = thread_cpu->env_ptr;
> @@ -819,6 +848,13 @@ static void host_signal_handler(int host_sig, siginfo_t *info, void *puc)
> if (host_sig == SIGSEGV) {
> bool maperr = true;
>
> + /* Did segfault happened in qemu source code? */
> + if ((pc >= (uintptr_t) &_init && pc < (uintptr_t) &_fini) ||
> + (TARGET_ABI_BITS == 32 && HOST_LONG_BITS == 64
> + && !h2g_valid(host_addr))) {
> + qemu_show_backtrace(info);
> + }
This is incorrect.
I did mention that you should look at adjust_signal_pc,
which has a lot of commentary on the subject.
(0) Place this after the write-protect and restart check
just below, since that is not an error of any sort.
(1) If helper_retaddr == 1, then this is a fault reading
for translation and is a guest SIGSEGV.
(2) If helper_retaddr != 0, then this is a fault in some
cpu_ldst.h operation and is a guest SIGSEGV.
(3) If in_code_gen_buffer(host_signal_pc()), then this
is a fault within generated code and is a guest SIGSEGV.
Otherwise it's a host SIGSEGV.
r~
next prev parent reply other threads:[~2023-08-12 17:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 16:43 [PATCH] Fix signal handler to detect crashes in qemu-linux-user Helge Deller
2023-08-12 17:33 ` Richard Henderson [this message]
2023-08-12 18:12 ` Helge Deller
2023-08-13 2:30 ` Richard Henderson
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=56908f79-c883-0d83-c990-e7a86714b6da@linaro.org \
--to=richard.henderson@linaro.org \
--cc=deller@gmx.de \
--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).