lkml.org 
[lkml]   [2006]   [Jun]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: kernel module debugging question
From
Date
On Fri, 2006-06-30 at 12:28 +0000, s.a. wrote:
> Hi,
> I have got the following fault , can you provide me with more details
> about the problem ?
> Best Regards

Hi,

you disabled CONFIG_KALLSYMS in your kernel configuration, which means
the backtrace isn't really useful for anyone to look at (unless you run
ksymoops with the exact System.map)... the problem is that it only shows
the addresses of the bad guys, but not the names. Those addresses are
different for each compilation, and you can use YOUR System.map file to
decode. However it's a lot more robust to let the kernel decode it for
you by enabling CONFIG_KALLSYMS....

Greetings,
Arjan van de Ven



-
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/

\
 
 \ /
  Last update: 2006-06-30 12:03    [W:0.023 / U:0.196 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site