Kernel debugging ???

Mike Flouris (flouris@csi.forth.gr)
Tue, 18 Nov 1997 09:24:29 +0200


Hallo,

Could anyone suggest some way of debugging code in
the kernel, if there is one.

Well what I really want is to hunt down what happens
in my code using a page like the one below.

Is there such a thing ?
What's the best way of doing this ?
Where in my system can I get more information about
the crash (besides /var/log/messages) ?

Thanx in advance,
Mike &

==========================

Unable to handle kernel paging request at virtual address c2994f38
current->tss.cr3 = 01715000, %cr3 = 01715000
general protection: 0000
*pde = 00f95b98
Oops: 0000
CPU: 0
EIP: 0010:[<0016ad55>]
EFLAGS: 00010006
eax: 0375b0cc ebx: 02994f18 ecx: 00000019 edx: 0028be60
esi: 001b55c4 edi: 002af298 ebp: 00000400 esp: 03d39cb8
ds: 0010 es: 0018 fs: 002b gs: 002b ss: 0018
Corrupted stack page
Process update (pid: 185, process nr: 20, stackpage=03d39000)
Stack: 000000ee 001b55c4 001c6264 001c6101 0016fc39 00000001 002af298 002af298
001c6264 0016fbcc 00000424 0016cd86 001c6264 002ab0f8 20000000 0000000f
0010ca3a 0000000f 002af298 00000000 000003fe 00c0d14a 400d6154 0010c891
Call Trace: [<0016fc39>] [<0016fbcc>] [<0016cd86>] [<0010ca3a>] [<0010c891>]
[<0012818f>] [<00122270>]
[<0010a665>]
Code: 8b 43 20 c1 e8 09 89 46 18 39 46 14 73 10 89 46 14 68 ac 69
Aiee, killing interrupt handler