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 21:19:12 +1000
Delivery-date: Fri, 15 Jun 2007 04:17:24 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <907625E08839C4409CE5768403633E0B02561E1B@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: <AEC6C66638C05B468B556EA548C1A77D01166AD8@trantor> <907625E08839C4409CE5768403633E0B02561E1B@xxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Aceu+eYcdhjPgJ+rRvugkSzn1LjW4wANhVDQAAHRtwAAABeP4AABXWMQ
Thread-topic: [Xen-users] qemu-dm crashing under 3.1
> 
> That would make it a lot more readable - you could try just "objdump
-d
> qemu-dm" and see if that gives you a clue of which function it's in,
but
> using a debug build would make it much more readable.
> 
> You can re-build JUST qemu-dm by going to .../tools/ioemu and doing
> "make clean all" - first modify the CFLAGS in makefile with "CFLAGS +=
> -g" to add debug symbols. Then copy your new qemu-dm to
> /usr/lib[64]/xen/bin on the target machine (if that's not the same
> machine you're building the code on).
> 

Because it was a debian build it needed a bit of persuasion...

Here's the output (excuse the line wrapping):

"
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 47890972539360 (LWP 4609)]
0x0000000000409b25 in main_loop_wait (timeout=10)
    at
/usr/local/src/xen/xen-3.1-3.1.0-rc10+hg15040/debian/build/source/tools/
ioemu/vl.c:5224
5224                if (ioh->fd_write && FD_ISSET(ioh->fd, &wfds)) {

(gdb) bt
#0  0x0000000000409b25 in main_loop_wait (timeout=10)
    at
/usr/local/src/xen/xen-3.1-3.1.0-rc10+hg15040/debian/build/source/tools/
ioemu/vl.c:5224
#1  0x000000000046c041 in main_loop ()
    at
/usr/local/src/xen/xen-3.1-3.1.0-rc10+hg15040/debian/build/source/tools/
ioemu/target-i386-dm/helper2.c:628
#2  0x000000000040b6d6 in main (argc=21, argv=0x7fff2fa03468)
    at
/usr/local/src/xen/xen-3.1-3.1.0-rc10+hg15040/debian/build/source/tools/
ioemu/vl.c:6903

(gdb) print ioh
$1 = (IOHandlerRecord *) 0x9224b0
(gdb) print ioh->fd_write
$2 = (IOHandler *) 0x4691e0 <vnc_client_write>
(gdb) print ioh->fd
$3 = 9932400
(gdb) print wfds
$4 = {fds_bits = {0 <repeats 16 times>}}
(gdb) print &wfds
$5 = (fd_set *) 0x7fff2fa00760
(gdb)
"

The only thing that strikes me as odd is the value of ioh->fd... isn't
that a little bit high for a fd number?

James

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