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-devel

Re: [Xen-devel] Reproducible system crash

To: xen-devel@xxxxxxxxxxxxxxxxxxxxx, Peter Joanes <pjoanes@xxxxxxxxxxx>
Subject: Re: [Xen-devel] Reproducible system crash
From: Kip Macy <kip.macy@xxxxxxxxx>
Date: Wed, 16 Mar 2005 11:35:46 -0800
Delivery-date: Wed, 16 Mar 2005 19:37:31 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=sat6cb0ckHGjUZJDE152Zde+xTeUufGduPMKPV4Hq0rYpSM2sjI+5QOgrIkGgmY6ubvqWLx1arfiM6YMWgFhniN5TFicxQ9bvrIQgvVZbNxcMyPOoVHZkcTFyp6PrKKR9S1uS8A6OU9w+5vQc7Qs7DkiRjkQOInZShk10g4GMvw=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <240b7ae935630db1625e232e965650a4@xxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D1E36C8@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <240b7ae935630db1625e232e965650a4@xxxxxxxxxxxx>
Reply-to: Kip Macy <kip.macy@xxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
Real men don't use debuggers ;-) but for those of us who do:

gdb vmlinux 
(gdb) x/i 0xc01099a 

will do the same thing. If you have symbols compiled in, you can also do :

(gdb) info line *0xc01099a 

and get the exact line of C code.

  -Kip

> The stack backtrace also indicates that the code at address 0xc010990a
> in XenLinux may also be interesting (that is the code point that caused
> the crash).
> 'objdump -d vmlinux' and then grep the output for that address....
>


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel