DEBUG-ALERT attribute
- Last Updated: October 30, 2020
- 1 minute read
- OpenEdge
- Version 12.2
- Documentation
Indicates whether the AVM provides access to ABL and .NET stack trace information, where applicable, when an error occurs during a session. Its primary use is for error alert boxes, so you can determine where an error occurred in your code.
Data type: LOGICAL
Access: Readable/Writeable
Applies to: SESSION system handle
When an unhandled ABL error or .NET Exception occurs 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, which when pressed, produces a Stack Trace dialog box
containing ABL 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 ABL and .NET
stack traces are also 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.
You can also set DEBUG-ALERT to TRUE using
the Debug Alert (-debugalert) startup parameter. For more
information see Startup Command and Parameter Reference.
For more information about debugging from an alert dialog box, see Troubleshoot ABL Applications.