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 10:45:46 -0700 Message-ID: <49BD3ECA.1050409@goop.org> References: <49BAFC72.4040501@goop.org> <49BB0184.1020503@goop.org> <49BB6F4A.90000@gmail.com> <49BC2994.6040404@goop.org> <49BCE8F6.50504@gmail.com> <49BD1F87.8040008@goop.org> <49BD3E3D.6000607@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: <49BD3E3D.6000607@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: > Jeremy Fitzhardinge schrieb: > =20 >> Sven K=F6hler wrote: >> =20 >>>> Can you get a coredump from the fault and see what the faulting >>>> instruction was? >>>> =20 >>>> =20 >>> How do I do that? >>> Sorry for the stupid question, but unfortunatly this is beyond my >>> knowledge of the tooldchain :-( >>> =20 >> $ 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. >> =20 > > # ulimit -c unlimited > # ./a.out > Segmentation fault (core dumped) > # gdb a.out core > GNU gdb 6.8 > Copyright (C) 2008 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later > > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. Type "show copyi= ng" > and "show warranty" for details. > This GDB was configured as "x86_64-pc-linux-gnu"... > Core was generated by `./a.out'. > Program terminated with signal 11, Segmentation fault. > [New process 13256] > #0 0xf7f3642f in __kernel_vsyscall () > (gdb) x/i $eip-2 > 0xf7f3642d <__kernel_vsyscall+13>: jmp 0x25f4278f > (gdb) > =20 Hm. How about "x/30i __kernel_vsyscall"? J