Is there a good primer on reading an Oops? I'm also looking for general tips
on configuring the kernel and my module so that a useful stack trace is
generated - entry points show function names rather than addresses. The
obvious is to build with debugging turned on but is it necessary for the
kernel to be built with debugging turned on to effectively trace back
through a crash? It seems that the Oops in the messages log resolves symbols
but on the console I only get function addresses.
Jerry Kelley
jkelley@iei.net
-
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/
This archive was generated by hypermail 2b29 : Sun Oct 15 2000 - 21:00:16 EST