[lkml]   [2000]   [Oct]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subjectinfo on Oops
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

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:39    [W:0.029 / U:0.320 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site