Debugging Smalltalk errors

If your application encounters an error while running on the target environments Windows, AIX, Sun Solaris, or Linux, the resultant dump can be debugged using one of the following types of debug support:

•	Stack trace

•	Stack dump debugger

•	Interactive debugger

These three types of debug support provide backup for one another. If a Smalltalk error occurs, some level of information is always available to you. For example, the interactive debugger requires a communication connection between the workstation and the target platform. If this connection cannot be attained, the debugger attempts to produce output for use with the stack dump debugger.

Regardless of which debugger you are using, the best results come when the debugger can access the snapshot file (with a file extension of snp) taken at the time your image was packaged. When a debugger is started, the search mechanism looks for the snapshot file associated with the image in error. Smalltalk searches in the following sequence:

1.	In the output directory the packaging instructions specify

2.	In the current working directory

3.	In the directory the image component resides in, as specified by the system's abt.ini file

4.	In the directories specified by the method snapshotPath

5.	In the library

To view the correct source code associated with the failing image, ensure that the snapshot file is in a place Smalltalk will search.