WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

RE: [Xen-users] qemu-dm crashing under 3.1

To: "Petersson, Mats" <Mats.Petersson@xxxxxxx>, <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] qemu-dm crashing under 3.1
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Fri, 15 Jun 2007 20:25:33 +1000
Delivery-date: Fri, 15 Jun 2007 03:24:20 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <907625E08839C4409CE5768403633E0B02561E17@xxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <AEC6C66638C05B468B556EA548C1A77D01166AC1@trantor> <907625E08839C4409CE5768403633E0B02561E17@xxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Aceu+eYcdhjPgJ+rRvugkSzn1LjW4wANhVDQAAHRtwA=
Thread-topic: [Xen-users] qemu-dm crashing under 3.1
> >
> > I've had two unexplained instances now of qemu-dm crashing for no
> > apparent reason, and with no clue as to why. There is nothing
> > in the log
> > files or anything.
> >
> > I know I can get it to crash by doing funky things with vnc,
> > but I don't
> > believe that that was the case here...
> >
> > Any suggestions? Is this a known problem that is fixed by a patch
> > anywhere?
> 
> How about connecting gdb to the qemu-dm (find the PID for qemu, then
in
> gdb do "attach <pid>; c". When it crashes or exits, it will catch it
in
> gdb, and you'll be able to do a traceback (at least if it didn't just
> exit with an error code).
> 
> I've not seen any problem like this, nor any fix for it.

Okay... I can produce a segfault in a windows domain with vnc, but not
in a linux domain in text mode.

'backtrace' says:

"
#0  0x0000000000409b25 in ?? ()
#1  0x000000000046c041 in ?? ()
#2  0x000000000040b6d6 in ?? ()
#3  0x00002b43022004ca in __libc_start_main () from /lib/libc.so.6
#4  0x0000000000404bba in ?? ()
#5  0x00007fffa94a6f08 in ?? ()
#6  0x0000000000000000 in ?? ()
"

Which isn't helpful to me. Is there another command I can try to give
something more useful? Perhaps I need debug info compiled in...

Thanks

James

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