From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Richard Henderson <richard.henderson@linaro.org>,
Helge Deller <deller@gmx.de>,
qemu-devel@nongnu.org
Subject: Re: [PATCH][RFC] Add crash handler for qemu-linux-user
Date: Thu, 17 Aug 2023 11:58:50 +0100 [thread overview]
Message-ID: <ZN39ann2QV3Jsx+z@redhat.com> (raw)
In-Reply-To: <CAFEAcA_yD37zTnXNkX+qg_WtUUQPJrk72UL4vusdJrnNHz4H7A@mail.gmail.com>
On Thu, Aug 10, 2023 at 10:14:06AM +0100, Peter Maydell wrote:
> On Thu, 10 Aug 2023 at 02:28, Richard Henderson
> <richard.henderson@linaro.org> wrote:
> >
> > On 8/9/23 16:07, Helge Deller wrote:
> > > + /* did qemu source code crashed? */
> > > + if (unlikely(!h2g_valid(host_addr))) {
> > > + qemu_show_backtrace(info);
> > > + }
> >
> > This won't do anything at all when reserved_va == 0,
> > i.e. 64-bit guest on 64-bit host, or any 32-bit host.
> >
> > The idea of having a backtrace is nice, I suppose, we just need
> > a better detector.
>
> I think Dan also had a look at one point at doing
> backtraces for crashes in system emulation mode?
> Certainly this would be useful for test crashes in CI.
I stopped that work as I couldn't figure out a way to get a backtrace
across all the threads, which severely limited its usefulness in the
QEMU system emulators.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2023-08-17 11:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 23:07 [PATCH][RFC] Add crash handler for qemu-linux-user Helge Deller
2023-08-10 1:27 ` Richard Henderson
2023-08-10 9:14 ` Peter Maydell
2023-08-17 10:58 ` Daniel P. Berrangé [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=ZN39ann2QV3Jsx+z@redhat.com \
--to=berrange@redhat.com \
--cc=deller@gmx.de \
--cc=peter.maydell@linaro.org \
--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).