Re: [Xen-devel] Re: 2.6.28.7 domU: 32-bit emulation seems to be broken

[Jeremy Fitzhardinge <jeremy@xxxxxxxx>]

Sven Köhler wrote:
> Jeremy Fitzhardinge schrieb:
>   
> > Sven Köhler wrote:
> >     
> > > > Can you get a coredump from the fault and see what the faulting
> > > > instruction was?
> > > >     
> > > >         
> > > 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.
> >     
> # 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
> <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> 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)
>   
Hm.  How about "x/30i __kernel_vsyscall"?

   J

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel