106 ``gdb`` is easier, but the Kernel should be pre-compiled with debug info.
108 gdb  section in Finding the bug's location
111 The GNU debugger (``gdb``) is the best way to figure out the exact file and line
114 The usage of gdb works best on a kernel compiled with ``CONFIG_DEBUG_INFO``.
126   $ gdb vmlinux
127   (gdb) l *0xc021e50e
138   $ gdb vmlinux
139   (gdb) l *vt_ioctl+0xda8
154   (gdb) p vt_ioctl
156   (gdb) l *0xae0+0xda8
161   $ gdb drivers/tty/vt/vt_ioctl.o
162   (gdb) l *vt_ioctl+0xda8
173 in gdb and list the relevant code::
175   $ gdb fs/jbd/jbd.ko
176   (gdb) l *log_wait_commit+0xa3
187 	$ gdb drivers/media/usb/dvb-usb/dvb-usb.o
188 	(gdb) l *dvb_usb_adapter_frontend_exit+0x3a