| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] Xen & Transmeta (from xen-users)
On Wed, 1 Jun 2005, Keir Fraser wrote:
>
> 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.
Excellent!
The sysms file is available at
[http://www.cs.rit.edu/~cwh0803/xen/xen-2.0-testing-syms].
A note about the symbols -- there are strings I've added for debug/tracing
purposes, most of which are of the form ' -> XXX'...
The debug dump is as follows (let me know if you need more):
========== BEGIN DEBUG DUMP ==========
Initializing CPU#0
ACPI: RSDP (v000 OID_00 ) @ 0x000e4010
CPU: 0
EIP: 0808:[<fc5349c0>]
EFLAGS: 00210086
eax: ffff27c0 ebx: 0e7fb7c0 ecx: 00000000 edx: 00000000
esi: fc4e4010 edi: 00000024 ebp: 0e7fb7c0 esp: fc503c20
ds: 0810 es: 0810 fs: 0810 gs: 0810 ss: 0810
Stack Trace from ESP=fc503c20:
{NOT DISPLAYED}
Call Trace from ESP=fc503c20: [<fc525520>] [<fc5237f0>] [<fc50400c>]
Faulting linear address might be ffff27c4
CPU0 FATAL TRAP 14 (page fault), ERROR_CODE 0009, IN INTERRUPT CONTEXT
=========== END DEBUG DUMP ===========
Please let me know if you need anything else or want me to try stuff..
Thanks for your help!
Carl
- --
"There are 10 types of people in the world: Those who understand binary
and those that don't."
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home