> Hi,
>
> I'm running 2.0.31-pre10 on a P90, 64Mb, 2940UW scsi system.
> I was using vi in an xterm, with a number of xterms and about 25 dial-in PPP
> sessions. The vi died and I got the following in my system log...
>
> invalid operand: 0000
> CPU: 0
> EIP: 0010:[<000000b3>]
> EFLAGS: 00010202
> eax: 00000000 ebx: 00000000 ecx: 00000000 edx: 00000000
> esi: 00000000 edi: 00000000 ebp: 08038e30 esp: 01b5be88
> ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
> Process vi (pid: 8541, process nr: 113, stackpage=01f5b000)
> Stack: 00000000 00000011 000000b3 00000000 00000000 00000011 ffffffb3 00000000
> 00000000 00000029 08038cd8 00000000 00000000 00000000 00000033 08038e90
> 08038ea0 000000b3 00000000 00000011 000000b3 00000000 00000000 00000011
> Call Trace:
> Code: f0 53 ff 00 f0 53 ff 00 f0 53 ff 00 f0 53 ff 00 f0 53 ff 00
> task already on run-queue
Another totally (or is it just mostly?) useless bug report with no address
to symbol translation. Has anyone considered setting up an autoresponder
that perhaps scans messages for
"EIP:[:space:]+[0-9]+:\[<[0-9]"
and if it doesn't find
"Using .* to map addresses to symbols"
in the remainder of the body fires off a message to the original sender
about how you have to run that through ksymoops using the appropriate
System.map for it to be at all useful? It seems like the sort of thing
that could be done relatively easily in procmail.
------------------------------------------------------------------
Jon Lewis <jlewis@fdt.net> | Unsolicited commercial e-mail will
Network Administrator | be proof-read for $199/message.
Florida Digital Turnpike |
______http://inorganic5.fdt.net/~jlewis/pgp for PGP public key____