HTCondorWiki: Daemon Debugging

 For the adventurous (or those who are debugging the clone calls), one can apply the patch found on #2208
 
 
+{subsection: Debug a core file produced by a stripped binary}
+
+Say you have a.out.stripped and a.out.with_symbols.  And say you have a core file from a.out.stripped that you want to debug, but are being thwarted by the lack of symbols.  The trick is you still want to gdb the file that produced the core, but load symbols from the unstripped binary into the text segment of the file you are debugging.
+
+   % gdb a.out.stripped core
+
+... gdb will complain about missing debug info ...
+
+   (gdb) maint info sections
+
+In the output from 'maint info sections', look for .text section. The address that is in the first column is what you want to use in the next command.  For instance, one of the output lines from 'maint info sections' will be
+
+    0x00400390->0x00400588 at 0x00000390: .text ALLOC LOAD READONLY CODE HAS_CONTENTS
+
+The address in the first column, 0x00400390 in this example, is used in the next gdb command:
+
+   (gdb) add-symbol-file a.out.with_symbols 0x00400390
+
+Of course, substitute 0x00400390 with the proper text segment address.
+
+Now you should be able to do a backtrace, etc.
+