Hi all,
I was searching on the net for solving oops. This thread/discussion
helped me alot.
Thanks to all.
I tried objdump & gdb on vmlinux. Using this, i am able to get
information about kernel functions & their symbols.
Now, if a module (created by a used) is giving kernel-panic/oops
messages, then whether objdump/gdb will give info for that module also
? The module will be loaded separately(not built-in module).
OR
how to detect/trace a module symbol/function causing panic/oops ?
Any help/links/reference is welcome.
TIA,
Yogeshwar
On Thu, Jun 12, 2008 at 9:45 PM, Wenhua Zhao <whzhao@xxxxxxxxx> wrote:
>
> Hi,
>
> "Mulyadi Santosa" <mulyadi.santosa@xxxxxxxxx> writes:
>
>> On Thu, Jun 12, 2008 at 7:23 PM, jasjit singh <singh.jasjit@xxxxxxxxxxx> wrote:
>>>
>>> My question is how I can decipher the constant values that are added to
>>> (perhaps) function pointers.
>>> e.g 412 in {chrdev_open+412}.
>>
>> that's...IIRC.... the offset from the beginning of function.
>>
>>> Can these figures be actually helpful in getting what exactly caused kernel
>>> to panic ?
>>
>> yes, just disassemble your vmlinux file...
>>
>
> If you have you kernel compiled with the debug enabled, then you can
> do
>
> objdump -S vmlinux
>
> It will interleave the source with the compiled assembly
> instructions. Very easy to locate the problem.
>
>
> Regards,
> Wenhua
>
> --
> To unsubscribe from this list: send an email with
> "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
> Please read the FAQ at http://kernelnewbies.org/FAQ
>
>
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ
