Re: 5.0R: Panic

From: Alexander Langer <alex(at)big.endian.de>
Date: Wed, 19 Feb 2003 17:24:08 +0100

Thus spake Patric Mrawek (patric(at)argv.de):
> Faellt dazu jemandem was Schlaues ein?
> Fatal trap 12: page fault while in kernel mode
> fault virtual address = 0x32
> fault code = supervisor read, page not present
> instruction pointer = 0x8:0xc020c793
> stack pointer = 0x10:0xd8e9aad8
> frame pointer = 0x10:0xd8e9ab0c
> code segment = base 0x0, limit 0xfffff, type 0x1b
> = DPL 0, pres 1, def32 1, gran 1
> processor eflags = interrupt enabled, resume, IOPL = 0
> current process = 35612 (jpilot-sync)
> trap number = 12
> panic: page fault
> #12 0xc0370f70 in trap (frame=
> {tf_fs = 24, tf_es = 16, tf_ds = 16, tf_edi = -655774924, tf_esi = -2144570347, tf_ebp = -655774964, tf_isp = -655775036, tf_ebx = -995056244, tf_edx = -655774924, tf_ecx = 21, tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip = -1071593581, tf_cs = 8, tf_eflags = 66050, tf_esp = -997833984, tf_ss = -2144570347}) at ../../../i386/i386/trap.c:445

Mal bis hierhin "up"en, und dann wie im Developers Handbuch:
36:(kgdb) frame frame->tf_ebp frame->tf_eip

Das liefert Dir die Stelle, wo der Trap auftrat, und dort kannst Du mit
"list" direkt sehen, an welcher Stelle. Und das kann man dann fixen.

Ciao

Alex

To Unsubscribe: send mail to majordomo(at)de.FreeBSD.org
with "unsubscribe de-bsd-questions" in the body of the message
Received on Wed 19 Feb 2003 - 17:24:12 CET

search this site