The files used by GoBug
GoBug.exe
GoBugSpy.dll
GoBug.ini
GoBug.chm
System files used by GoBug

GoBug.exe
This is the main executable of the debugger. You can run two or more copies of GoBug at once either by making a copy of this file with a different name, or by running GoBug in a different directory (if you do this make sure the Dlls are there too). It might be useful to run a second copy of GoBug if you want to test two different debuggees at the same time. It will also allow you to run two or more copies of the debuggee at the same time if you wish (entirely seperately and in their own address space). This might be useful if you want to test how the debuggee works with shared files or data, or if you want to compare in real time how the debuggee reacts to different conditions. Note that a new .ini file will be made in the name given to the exe file. Also each copy of GoBug will attempt to register the same hot-key on start up. Either give them different hot-keys or run one copy without a hot-key.

GoBugSpy.dll
This file is injected into the debuggee's address space and is used by GoBug to hold the hooks necessary to receive messages destined for the debuggee and events which occur to the debuggee. You must not change the name of this file.

GoBug.ini
This file holds GoBug's configuration information. It is in coded format and cannot be altered except using GoBug itself. The information it holds includes size, position, colours and fonts. It also keeps the names of debuggees which were debugged in previous sessions together the breakpoints, inspectors and file paths used in those sessions. If, when GoBug starts, it cannot find the ini file, or if the ini file appears to be corrupted, a new one will be made using a default configuration. This is what happens when you first use GoBug because the GoBug.ini file is not shipped with it. If you change the name of GoBug.exe a new ini file will be made to match the new name.

GoBug.chm
This is the help file you are looking at now, in compressed hypertext markup format.

System files used by GoBug
GoBug relies on the Windows system files for its functionality, and it will not start if any of these are missing. If you are missing HHCTRL.OCX (a system file which shows this help file) run the self-extracting file hhupd.exe (help update). This is available from the Microsoft web site.