From: Avi Kivity <avi@redhat.com>
To: Mohammed Gamal <m.gamal005@gmail.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
mtosatti@redhat.com, kvm@vger.kernel.org
Subject: Re: [PATCH] Show registers and exit on unhandled errors
Date: Mon, 21 Sep 2009 14:51:30 +0300 [thread overview]
Message-ID: <4AB768C2.50204@redhat.com> (raw)
In-Reply-To: <52d4a3890909210431j3a1f9f7fpdec49963bfe3ed41@mail.gmail.com>
On 09/21/2009 02:31 PM, Mohammed Gamal wrote:
>
>> Don't we currently suspend the VM on unknown exits? This is more useful
>> than aborting as it allows to
>> - disassemble the problematic code
>> - poke around in the RAM
>> - look at other VCPUs
>> - attach a debugger to qemu
>> - ...
>>
>>
> Good point. But at least we can still show registers, since that also
> can give some diagnostic information, no?
>
There's 'info registers' for that.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-09-21 11:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-21 11:18 [PATCH] Show registers and exit on unhandled errors Mohammed Gamal
2009-09-21 11:29 ` Jan Kiszka
2009-09-21 11:31 ` Mohammed Gamal
2009-09-21 11:42 ` Jan Kiszka
2009-09-21 11:47 ` Mohammed Gamal
2009-09-21 11:50 ` Mohammed Gamal
2009-09-21 11:51 ` Avi Kivity [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=4AB768C2.50204@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=m.gamal005@gmail.com \
--cc=mtosatti@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.