From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Re: 2.6.28.7 domU: 32-bit emulation seems to be broken Date: Sun, 15 Mar 2009 08:32:23 -0700 Message-ID: <49BD1F87.8040008@goop.org> References: <49BAFC72.4040501@goop.org> <49BB0184.1020503@goop.org> <49BB6F4A.90000@gmail.com> <49BC2994.6040404@goop.org> <49BCE8F6.50504@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <49BCE8F6.50504@gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?ISO-8859-15?Q?Sven_K=F6hler?= Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Sven K=F6hler wrote: >> Can you get a coredump from the fault and see what the faulting >> instruction was? >> =20 > > How do I do that? > Sorry for the stupid question, but unfortunatly this is beyond my > knowledge of the tooldchain :-( $ ulimit -c unlimited $ ./a.out Segmentation Fault (core dumped) $ ls core.* core.XXXXX $ gdb ./a.out core.* [...] (gdb) x/i $eip-2 It will help to compile your a.out with -g. J