From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kip Macy Subject: Re: garbage registers when domain killed by xen Date: Sat, 7 May 2005 09:02:29 -0700 Message-ID: References: <1bea7043d407c09e23b119c6c278dbe3@cl.cam.ac.uk> <902dfdb94d996d7fc05e0c8313c10886@cl.cam.ac.uk> Reply-To: Kip Macy Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <902dfdb94d996d7fc05e0c8313c10886@cl.cam.ac.uk> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel List-Id: xen-devel@lists.xenproject.org On 5/7/05, Keir Fraser wrote: > It's probably repeatedly reentering your p-f handler at address 0.=20 Sounds about right. >=20 > Yes, we should just domain_crash() if we see a callback to address 0. Your patch or mine? ;-) > Even more helpful would be some extra crash context with an explanation > (some way of stating it was a virtual 'double fault' of some kind), but > I don;t know how you would represent that in a standard core dump file. One could add a set of flags to the dump. They wouldn't be visible to GDB, but we could have a core reading utility that could see it and spit out some basic info about the crash. GDB wouldn't need it per se' as it would look just like a SIGSEGV crash in an application. -Kip