Finding offending C code line after Oops ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



My driver module is causing a GPF.

The Oops is telling me it occurs in func_a() at offset 0xD5.

I've done a 
 # objdump -D -g mymod.o

But this only gets me the assembly for that function.  My assembly is poor
at best.  

Is there a way to splice in the C code for that function so I can see the
offending C code line ?

I've read the IBM presentation at 
http://www-124.ibm.com/linux/presentations/lwce2002sf/debug/Debug_linuxworld
2002.pdf
But that doesn't discuss matching the C code to the offset.

GDB matches up code to assembly (I think?) so this must be possible...right
?

I haven't compiled with optimizations.

Any help really appreciated
Thanks
dom

--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux