Differences between current version and previous revision of KernelDevelopmentDebugging.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 4 | Last edited on Wednesday, January 18, 2006 2:46:08 pm | by IanMcDonald | |
| Older page: | version 3 | Last edited on Wednesday, October 19, 2005 7:35:08 pm | by AristotlePagaltzis | Revert |
@@ -4,8 +4,14 @@
objdump -r -S -l --disassemble net/dccp/ipv4.o
</verbatim>
NB.: you need to be at the top level of the kernel tree for this to pick up your [C] files.
+
+The stack trace will have lines something like:
+<verbatim>
+dccp_sendmsg+0x135/0x17f
+</verbatim>
+The 0x135 is offset from the start of the function. The 0x17f is the total function length. The output from objdump shows byte in absolute format from start of file so you will need to add the offset to the start of the function and then you will find your line of code.
If you don't have access to the code you can also debug on some crash dumps e.g. crash dump output as shown by Dave Miller.
> <verbatim>
