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/
Home Products Support Community News


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

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Re: domU: 32-bit emulation seems to be broken
From: Sven Köhler <sven.koehler@xxxxxxxxx>
Date: Sun, 15 Mar 2009 18:43:25 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 15 Mar 2009 10:44:36 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type; bh=vfM9oR8DkrRRYs+Zi1XD+9rHzGmC7kcTfXTiwvngnbw=; b=PF8olAEAOtdAM+b7uHU3NQfqQ19Vuu9YZV3aa6dHXtiZSna5svAArfl7mh0DfXMtqz VGE1pYvJBicCRYrFAyC/5dbqWOajhdVV5cme+4ZabR5Hm65JshJr5sMurRo8sBOZL7z2 Q5XFzM4B0X2P8UQ9ra15G93NA14oBwHht7od8=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type; b=QUUyp2nL1erd60qSlZ7Qms9s5gSaOxSZTKwDvpAZlIMTjetFT0+8wk19WOe+eIXI7E lHSdM49U+L/4jEg1rJmKWahIg/4/8+mRkhhERyea5Sd3aUnbk4QmMKrkDDjBAMzoBP9V IawZMHJHGXDXqoSYmGsYk28Pr+uThp18wF1ps=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <49BD1F87.8040008@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <gpe0vg$j67$1@xxxxxxxxxxxxx> <gpei6e$gcn$1@xxxxxxxxxxxxx> <49BAFC72.4040501@xxxxxxxx> <49BB0184.1020503@xxxxxxxx> <49BB6F4A.90000@xxxxxxxxx> <49BC2994.6040404@xxxxxxxx> <49BCE8F6.50504@xxxxxxxxx> <49BD1F87.8040008@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (Windows/20081209)
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
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

Attachment: signature.asc
Description: OpenPGP digital signature

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>