From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH] Show registers and exit on unhandled errors Date: Mon, 21 Sep 2009 14:51:30 +0300 Message-ID: <4AB768C2.50204@redhat.com> References: <1253531881-3847-1-git-send-email-m.gamal005@gmail.com> <4AB763B4.9060603@siemens.com> <52d4a3890909210431j3a1f9f7fpdec49963bfe3ed41@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Jan Kiszka , mtosatti@redhat.com, kvm@vger.kernel.org To: Mohammed Gamal Return-path: Received: from mx1.redhat.com ([209.132.183.28]:42080 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751384AbZIULvk (ORCPT ); Mon, 21 Sep 2009 07:51:40 -0400 In-Reply-To: <52d4a3890909210431j3a1f9f7fpdec49963bfe3ed41@mail.gmail.com> Sender: kvm-owner@vger.kernel.org List-ID: 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