lkml.org 
[lkml]   [1996]   [Mar]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: on debugging loadable modules...
   Date: 	Thu, 14 Mar 1996 12:57:53 +1100 (EST)
From: Keith Owens <kaos@audio.apana.org.au>

Problem with running ksymoops after the event is that the current
system might not match the modules running when the oops occurred.
ksymoops would have to read all the way through a log to work out
which modules were loaded at the oops point, messy.

Agreed.

Suggest that the loaded module data be printed as part of the oops,
one off data instead of log scanning and interpretation.

Yeah, have some module_map registry linked list of some sort, and if
module support is enabled oops calls print_module_mappings() or
something like that. I like this idea.

Later,
David S. Miller
davem@caip.rutgers.edu


\
 
 \ /
  Last update: 2005-03-22 13:36    [from the cache]
©2003-2014 Jasper Spaans. Advertise on this site