lkml.org 
[lkml]   [1998]   [Apr]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: How to understand a kernel oops message?
Date
From
Gabriel Paubert <paubert@iram.es> said:
> On Thu, 2 Apr 1998, Foo Chun Choong wrote:

[...]

> > (2) In EIP:[dev_ioctl+476/508] is there a way for me to find the exact
> > line of the kernel code that is causing the problem (using 476/508??)

> There are several possibilities, use ksymoops as a first step. I often
> prefer to objdump the .o file because I can have a look at the code
> before the oops. You may also try gcc -S with the same options used to
> compile the kernel (the -fverbose-asm switch does not seem to help in
> getting more readable output).

Better: Compile with "-S -g" (plus the exact same flags used in the kernel
compilation! You saved the output of the "make", didn't you? :), then
search for the instructions the Oops gave you (the addresses will obviously
be written differently in the assembly source). The .stabs line before the
code should tell you (last number) which C source line it is.
--
Dr. Horst H. von Brand mailto:vonbrand@inf.utfsm.cl
Departamento de Informatica Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria +56 32 654239
Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

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