Answer by accessory for Kernel stack trace to source code lines
With gdb, you can also use this command to find the line number quickly:(gdb) list *(some_function+0x12c)
View ArticleAnswer by wenjianhn for Kernel stack trace to source code lines
Install kernel-debuginfoDownload decode_stacktrace.sh which is in the kernel source tree.Make stack dump output useful again. # ./decode_stacktrace.sh /usr/lib/debug/lib/modules/`uname -r`/vmlinux...
View ArticleAnswer by Johannes Thoma for Kernel stack trace to source code lines
If addr2line should print a question mark for line number or objdump fails to inline source code and you have a custom kernel, be sure to recompile the kernel with CONFIG_DEBUG_INFO set. You might need...
View ArticleAnswer by Lekensteyn for Kernel stack trace to source code lines
Given an unstripped vmlinux with debugging symbols (typically included with "linux-devel" or "linux-headers" packages matching your kernel version), you can use the addr2line program included with...
View ArticleAnswer by dawud for Kernel stack trace to source code lines
I don't have a ~= RHEL5 at hand, so the output shown is from a Fedora 20, though the process should be mostly the same (the name of the function has changed).You'd need to install the appropriate...
View ArticleKernel stack trace to source code lines
Given a kernel stack trace as below, how do you determine the specific line of code where the issue occurred?kernel: [<ffffffff80009a14>] __link_path_walk+0x173/0xfb9kernel:...
View Article