Commit:     926b28984da035ac407e6b8f22ee8b4f94f51cf1
Parent:     0a920b5b666d0be8141bd1ce620fffa7de96b81b
Author:     Pekka Enberg <[EMAIL PROTECTED]>
AuthorDate: Fri Jun 1 00:46:50 2007 -0700
Committer:  Linus Torvalds <[EMAIL PROTECTED]>
CommitDate: Fri Jun 1 08:18:28 2007 -0700

    Documentation: How to use GDB to decode OOPSes
    Adds instructions how to use GDB to figure out the exact location of
    an OOPS to Documentation/BUG-HUNTING.
    Signed-off-by: Pekka Enberg <[EMAIL PROTECTED]>
    Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
    Signed-off-by: Linus Torvalds <[EMAIL PROTECTED]>
 Documentation/BUG-HUNTING |   24 ++++++++++++++++++++++++
 1 files changed, 24 insertions(+), 0 deletions(-)

diff --git a/Documentation/BUG-HUNTING b/Documentation/BUG-HUNTING
index 65b97e1..35f5bd2 100644
--- a/Documentation/BUG-HUNTING
+++ b/Documentation/BUG-HUNTING
@@ -191,6 +191,30 @@ e.g. crash dump output as shown by Dave Miller.
 >        mov        0x8(%ebp), %ebx         ! %ebx = skb->sk
 >        mov        0x13c(%ebx), %eax       ! %eax = inet_sk(sk)->opt
+In addition, you can use GDB to figure out the exact file and line
+number of the OOPS from the vmlinux file. If you have
+CONFIG_DEBUG_INFO enabled, you can simply copy the EIP value from the
+ EIP:    0060:[<c021e50e>]    Not tainted VLI
+And use GDB to translate that to human-readable form:
+  gdb vmlinux
+  (gdb) l *0xc021e50e
+If you don't have CONFIG_DEBUG_INFO enabled, you use the function
+offset from the OOPS:
+ EIP is at vt_ioctl+0xda8/0x1482
+And recompile the kernel with CONFIG_DEBUG_INFO enabled:
+  make vmlinux
+  gdb vmlinux
+  (gdb) p vt_ioctl
+  (gdb) l *(0x<address of vt_ioctl> + 0xda8)
 Another very useful option of the Kernel Hacking section in menuconfig is
 Debug memory allocations. This will help you see whether data has been
 initialised and not set before use etc. To see the values that get assigned
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at

Reply via email to