Messages in this thread |  | | Date | Tue, 3 Sep 1996 21:48:03 -0700 | From | Steve VanDevender <> | Subject | oops |
| |
Never mind my last message; I found the "Oops" on the virtual console used by my X session. Since I don't have the stuff installed to do cut-and-paste from virtual consoles, or ksymoops, here's my laboriously hand-copied dump of the Oops and the interpretation from my kernel symbol table:
$ uname -a Linux tzadkiel 2.0.17 #43 Mon Sep 2 09:27:56 PDT 1996 i486
Oops: 0000 CPU: 0 EIP: 0010:[<00170ba3>] EFLAGS: 0010246 eax: 00000000 ebx: 004ed0000 ecx: 001c6ef4 edx: 01f6c810 esi: 009dd540 edi: 000000000 ebp: 00000000 esp: 01ca3f04 ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018 Process xterm (pid: 5670, process nr: 4, stackpage: 01ca3000) Stack: 009dd540 000000a7 001cce10 004ed000 0016f5c1 00000000 009dd540 00000000 004f0000 00000001 009dd180 004ed000 0016f74f 004ed000 001cce10 00178cd0 004ed000 004f0000 001705ff 004f0000 009dd180 009dd180 00d005b8 00d005b8 Call trace: [<0016f5c1>] [<0016f74f>] [<00178cd0>] [<001705ff>] [<00170a1a>] [<0012173c>] [<0012173c>] [<001217b8>] [<00121814>] [<0010a652>] Code: 66 8b 47 10 85 db 75 25 68 e8 b3 1b 00 25 ff ff 00 00 50 e8
00170ba3: tty_fasync+0x13 0016f5c1: do_tty_hangup+0x61 0016f74f: tty_hangup+0xf 00178cd0: pty_close+0x80 001705ff: release_dev+0x29f 00170a1a: tty_release+0xa 0012173c: __fput+0x1c 001217b8: close_fp+0x58 00121814: sys_close+0x44 0010a652: system_call+0x52
<code>: movw 0x10(%edi),%ax <code+4>: testl %ebx,%ebx <code+6>: jne $0170bd0 <code+8>: pushl $0x1bb3e8 (head_vals.418+0x49f) <code+13>: andl $0xffff,%eax <code+18>: pushl %eax
I hope I got that right.
|  |