Download GemBuilder for Smalltalk

Debugging
GemBuilder User Manual
• examine and modify objects and code within that context, and
• continue execution either normally or in single steps.
The Debugger’s stack pane displays the active call stack and allows you to choose
some context (stack frame) from that stack for manipulation in the window’s other
panes. The top contexts are GemStone Smalltalk contexts. If you can scroll
downward through the messages on the stack you will come to GS: Executed
Code: this is where the GemStone and client Smalltalk worlds meet. The contexts
below this point are client Smalltalk contexts.
If you select a GemStone Smalltalk context in the stack pane, the popup menu
contains the item show glue. This lets you reveal additional GemBuilder stack that
is normally of no interest. If this stack is already revealed, the menu item becomes
hide glue.
Like other GemBuilder text areas,the debugger source code pane provides
commands to execute GemStone Smalltalk, and it lets you examine step points and
set breakpoints.
Getting a Stack Trace Without a Debugger
In a situation in which you encounter an error but cannot use the Smalltalk
debugger (such as in a runtime application, or when the result is a virtual machine
crash), you can write a stack trace to a text file. To do so, execute:
GbsConfiguration dumpAllProcessStacks
In response, all processes in the image write their contexts to a file named
stacksAtx.txt in the current working directory, where x is a 10-digit number
derived from a time stamp.
5-28
GemStone Systems, Inc.
December 2001