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] Xen & Transmeta (from xen-users)

To: "Carl Holtje ;021;vcsg6;" <cwh0803@xxxxxxxxxx>
Subject: Re: [Xen-devel] Xen & Transmeta (from xen-users)
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 1 Jun 2005 14:37:25 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 01 Jun 2005 13:32:53 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <Pine.GSO.4.58.0506010917490.28466@xxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <Pine.GSO.4.58.0505241113400.16688@xxxxxxxxxxxxxxxx> <Pine.LNX.4.58.0505240925480.9339@xxxxxxxxxxxxxxx> <Pine.GSO.4.58.0505241128360.16688@xxxxxxxxxxxxxxxx> <Pine.LNX.4.58.0505240931540.9339@xxxxxxxxxxxxxxx> <4293878E.9090903@xxxxxxx> <Pine.GSO.4.58.0505251429370.20392@xxxxxxxxxxxxxxxx> <ecd2cfedbbd92a7bf208569b1e5fbeb1@xxxxxxxxxxxx> <Pine.GSO.4.58.0505261651450.20484@xxxxxxxxxxxxxxxx> <cd23d293fb9a3a92f4811bc17bfcca22@xxxxxxxxxxxx> <Pine.GSO.4.58.0505311542020.26084@xxxxxxxxxxxxxxxx> <6897e54f155e86bc8e55e2f33e69f51d@xxxxxxxxxxxx> <Pine.GSO.4.58.0506010917490.28466@xxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 1 Jun 2005, at 14:24, Carl Holtje ;021;vcsg6; wrote:

I can get you a register dump, the location the stack trace starts at
(ESP), the call trace from that point, and what it's determined to be the
faulty linear address -- is this enough?

Yes. The stack trace is the least useful bit, although it's sometime useful for working out what arguments were passed to functions in the backtrace.

 -- Keir


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