Messages in this thread |  | | From | Keith Owens <> | Subject | Re: silly [< >] and other excess | Date | Thu, 23 Nov 2000 14:03:21 +1100 |
| |
On Wed, 22 Nov 2000 21:54:48 -0500 (EST), "Albert D. Cahalan" <acahalan@cs.uml.edu> wrote: >Under NO circumstances should klogd or ksymoops mangle the >original oops. The raw oops data MUST be completely preserved. >It is a serious bug that this is not what currently happens.
ksymoops prints the original data followed by the decode, it is clean.
<rant> klogd only prints the decoded data, often gets it wrong and leaves garbage for ksymoops. I did a patch to klogd a couple of years ago and sent it to the maintainer but neither the sysklogd maintainer nor the distributors seem to care. </rant>
>The hard part of klogd/ksymoops is decoding the code bytes AFAIK. >The rest is a just a cross between grep and ps -- you search and >you do symbol lookups. I could throw it together in a few hours, >minus the disassembly part.
Take a look at the code in ksymoops oops.c before you make rash statements like that. It has to handle _all_ architecture messages, including cross arch debugging.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
|  |