Dave Hansen wrote:
>
> Badari Pulavarty wrote:
> > Code; c0160d0f <d_unhash+f/70> <=====
> > 0: 0f 0b ud2a <=====
> > Code; c0160d11 <d_unhash+11/70>
> > 2: 05 01 00 db 2a add $0x2adb0001,%eax
> > Code; c0160d16 <d_unhash+16/70>
> > 7: c0 (bad)
>
> Doesn't that (bad) instruction look suspicious? Martin was seeing
> strange oopses on Hummer (16-way NUMA-Q) compiling with egcs 2.91
> because it was generating bad instructions. It may be another
> problem, but that c0 jumped out at me. The two instructions after it
> look bretty bogus too.
We're encoding the file-and-line information in the program text
immediately after the undefined opcode, so you'll always see junk
in there. Sorry.
It would be much more useful if the oops code were to dump the
text preceding the exception EIP rather than after it, actually.
I think Keith said that ksymoops supports that.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Aug 15 2002 - 22:00:20 EST