Use Debug Alert (-debugalert) to access ABL and .NET stack trace information during a session. Its major use is for error alert boxes, so you can figure out where an error has occurred in your code.
Operating system and syntax
UNIX / Windows
-debugalert
Use with
Maximum value
Minimum value
Single-user default
Multi-user default
Client Session
—
—
—
—
Alternately, you can set the DEBUG-ALERT attribute on the SESSION system handle to TRUE in your application. The advantage of the DEBUG-ALERT attribute is that its value can be modified during a client session.
When an unhandled ABL error or .NET Exception occurs—there is no CATCH or NO-ERROR logic present—in an interactive session for any ABL client, the AVM displays an Error message box. When Debug Alert is TRUE, the message box also includes a Help button. Clicking on the Help button produces a Stack Trace dialog box containing ABL stack trace and .NET stack trace information. If the error was generated by throwing an error object from the ABL code and the Error Stack (-errorstack) startup parameter is used, or the ERROR-STACK-TRACE attribute on the SESSION system handle is set to true, then the stack trace also includes the contents of the CallStack property for the unhandled error. The stack trace information is written to the client log when the Client Logging (-clientlog) startup parameter is specified. The top of the stack (most recent call) is displayed at the top of the trace listing.
To retrieve or reset the value of this parameter at runtime, you use the DEBUG-ALERT attribute of the SESSION system handle. For more information on the DEBUG-ALERT attribute or the SESSION system handle, see OpenEdge Development: ABL Reference.
