From: Helge Deller <deller@gmx.de>
To: Richard Henderson <richard.henderson@linaro.org>, qemu-devel@nongnu.org
Cc: laurent@vivier.eu
Subject: Re: [PATCH v5 0/9] linux-user: Detect and report host crashes
Date: Fri, 13 Oct 2023 14:53:38 +0200 [thread overview]
Message-ID: <61512eb6-b999-48da-a2fb-58f6b3ec9b51@gmx.de> (raw)
In-Reply-To: <aa9f3112-7e34-4eff-8d93-59d036e82ff9@linaro.org>
On 10/13/23 05:52, Richard Henderson wrote:
> On 10/3/23 12:20, Richard Henderson wrote:
>> More signal cleanups. Mostly tested by temporarily adding an
>> abort, divide by zero, undefined instruction, null dereference,
>> within the implementation of a guest syscall to induce an error.
>>
>> Changes for v5:
>> * Remap guest abort, which means we need to try less hard on
>> the host side to handle assertion failures.
>> * Drop the backtrace. Since backtrace_symbols only looks at the
>> dynamic symbol set, we don't much that's useful -- we still
>> need to use the debugger.
I've attached this series on git head and did some basic tests.
My various chroots still work, and after adding some temporary code to trigger
a segfault in qemu code it works as expected and reports the fault.
So:
Acked-by: Helge Deller <deller@gmx.de>
Thank you!
Helge
prev parent reply other threads:[~2023-10-13 12:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 19:20 [PATCH v5 0/9] linux-user: Detect and report host crashes Richard Henderson
2023-10-03 19:20 ` [PATCH v5 1/9] linux-user: Split out die_with_signal Richard Henderson
2023-10-03 19:20 ` [PATCH v5 2/9] linux-user: Exit not abort in die_with_backtrace Richard Henderson
2023-10-03 19:20 ` [PATCH v5 3/9] linux-user: Detect and report host crashes Richard Henderson
2023-10-03 19:20 ` [PATCH v5 4/9] linux-user: Only register handlers for core_dump_signal by default Richard Henderson
2023-10-03 19:20 ` [PATCH v5 5/9] linux-user: Map unsupported signals to an out-of-bounds value Richard Henderson
2023-10-03 19:20 ` [PATCH v5 6/9] linux-user: Simplify signal_init Richard Henderson
2023-10-03 19:20 ` [PATCH v5 7/9] linux-user: Split out host_sig{segv,bus}_handler Richard Henderson
2023-10-03 19:20 ` [PATCH v5 8/9] linux-user: Detect and report host SIGILL, SIGFPE, SIGTRAP Richard Henderson
2023-10-03 19:20 ` [PATCH v5 9/9] linux-user: Remap guest SIGABRT Richard Henderson
2023-10-13 3:52 ` [PATCH v5 0/9] linux-user: Detect and report host crashes Richard Henderson
2023-10-13 12:53 ` Helge Deller [this message]
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=61512eb6-b999-48da-a2fb-58f6b3ec9b51@gmx.de \
--to=deller@gmx.de \
--cc=laurent@vivier.eu \
--cc=qemu-devel@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).