On Tue, 11 May 1999, RM wrote:
> i was wondering what techniques everyone was using to go about
> finding the causes of crashes, and lockups with the kernel. up to this
> point i've only really worked with device drivers, and having never worked
> with the kernel proper much, i don't have much of an idea on how to begin
> or go about it.
Always keep in proper place ( /boot ) the System.map file. After loading the
modules save the output of "ksyms". Compile your kernel with debugging (add
"-g" flag to gcc options in the linux/Makefile - in this way you can see the
source code in output from objdump -d --line-numbers --source - it is
best to dump one object file at a time after localising the function where
the exception occured - this will let you to find a line of source code with
the error).
There is more to ba said, this is just to get you started. There is a better
version of "ksymoops" program by Keith Owens <[EMAIL PROTECTED]>.
Regards,
--
Tomek
--- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
----
For more information on Real-Time Linux see:
http://www.rtlinux.org/~rtlinux/
