Differences between current version and revision by previous author of AdvancedDebuggingHints.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
| Newer page: | version 9 | Last edited on Friday, April 22, 2005 1:36:17 pm | by PerryLorier | |
| Older page: | version 7 | Last edited on Monday, September 13, 2004 9:08:31 am | by SamJansen | Revert |
@@ -41,7 +41,14 @@
continue
until 192
This runs some theoretical program with ''file.input'' as an argument, breaks in ''do_stuff'', displays ''g_my_stuff'' every time the program stops, continues twice past the ''do_stuff'' breakpoint, sets a temporary breakpoint in ''set_stuff'', continues till it hits this breakpoint, then continues until line 192. All of this is automated when you type ''gdb programname'' in the directory the ''.gdbinit'' resides in.
+
+!!!Checking the assembly
+Sometimes you hypothesize that the compiler is generating broken assembly (or generating assembly you didn't expect)
+ objdump -l -S --disassemble -r ''./foo''
+Will display the assembly intermixed with the source (if it was compiled with debugging symbols).
+
+
----
-CategorySoftwareEngineeringTools
+CategorySoftwareEngineeringTools CategoryProgramming
