Code and Data symbols
Viewing the code symbols
The code symbol "START" or "DLLSTART"
Viewing the data symbols
Dumping the code and data symbols
Printing the code and data symbols

Viewing the code symbols
The "inspect, exe/dll code symbols" menu item produces a modeless dialog in which you can view the code symbols of the debuggee and of loaded Dlls, provided symbols are available. The address of the code symbol is also given. This is the address in the debuggee's own address space. The name of the section is also given. You can also look at a list of code symbols in any Dlls if they are available. Use the drop down combo box to change which exe/dll is being looked at. You can create a code inspector by clicking the "View as code" button in this dialog.

The code symbol "START" or "DLLSTART"

If GoBug does not know the symbol at the executable's starting address it uses these simulated symbols instead. They will appear in the codepane or code inspector. They will also appear in symbol lists. Simulated symbols always appear in quotation marks. In fact, you will probably have given your program a symbol at the starting address which you have passed to the linker. However, since the starting address of the executable is held in the formal parts of the PE file itself, usually the linker will have discarded the name of the symbol itself. This is why GoBug may not know the symbol at the starting address and why it is necessary to simulate it.

Viewing the data symbols
The "inspect, exe/dll data symbols" menu item produces a modeless dialog in which you can view the data symbols of the debuggee and of loaded Dlls, provided symbols are available. The address of the data symbol is also given. This is the address in the debuggee's own address space. The name of the section is also given. You can also look at a list of data symbols in any Dlls if they are available. Use the drop down combo box to change which exe/dll is being looked at. You can create a data inspector by clicking the "View as data" button in this dialog.

Dumping the code and data symbols
Ensure that the code or data symbol dialog (as appropriate) is visible and go to the menu item "file, dump". Click on the appropriate dialog name which will appear in the menu item. Alternatively right click on the pane and choose "dump the pane". Choose a file name for the dumped file (GoBug will suggest a name). Choose a path for the file to be written (GoBug will remember this for the next time you debug this particular exe). Choose the type of file to make (use ANSI unless you want to make a Unicode file because you are using non-Roman characters in your code or data symbols). Code or data symbols are always dumped in full. The file which is created on this dump is plain text with carriage returns and line feeds but no tabs. It is usually best to view the dumped file with an editor set to a fixed width font (as opposed to a proportionally spaced font).

Printing the code and data symbols
Ensure that the code or data symbol dialog (as appropriate) is visible and go to the menu item "file, print". Click on the appropriate dialog name which will appear in the menu item. Alternatively right click on the pane and choose "print the pane". Code or data symbols are always printed in full (the number of pages appears in the print dialog). You can change the font used for printing by using the "settings, fonts, when printing" menu item.