Re: [Xen-devel] Why `xl restore` runs OK by shell but running on gdb encounter an segmentation fault?

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Tue, 2012-07-31 at 09:16 +0100, éç wrote:
> 
> 
> On Tue, Jul 31, 2012 at 2:55 PM, éç <aware.why@xxxxxxxxx> wrote:
>         Hi all,
>             I paste below the running info of `gdb xl`
>         Program received signal SIGSEGV, Segmentation fault.
>         0x000000000040a8a3 in create_domain (dom_info=0x7fffffffe4f0)
>         at xl_cmdimpl.c:1432
>         (gdb) bt
>         #0  0x000000000040a8a3 in create_domain
>         (dom_info=0x7fffffffe4f0) at xl_cmdimpl.c:1432
>         #1  0x000000000040f938 in main_restore (argc=2,
>         argv=0x7fffffffe6b8) at xl_cmdimpl.c:2932
>         #2  0x000000000040508b in main (argc=2, argv=0x7fffffffe6b8)
>         at xl.c:141
>         (gdb) show args
>         Argument list to give program being debugged when it is
>         started is "-v restore ./xp101.save".
>         
>         
>             Actually, in the shell I could run `xl -v
>         restore ./xp101.save` successfully.
>             Did anyone encounter the same wired problem? 
>         
>         
>         thanks in advance
>  
> I need to dig into xl  by gdb,  could anyone kind-hearted help me get
>  through this problem...

You need to be more patient -- you left around 80 minutes between your
original mail and this ping. Remember that not everyone is awake and
online at the same times as you are, nor can they be expected to drop
everything to reply to your mail.

I'm afraid that "gdb --args xl -v restore SAVED" works fine for me.

I presume that running under gdb perturbs timings or memory layout etc
to expose a previously latent bug.

gdb has given you the line numbers of where the segmentation fault has
occurred -- why don't you investigate further?

Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel