The -debugalert parameter adds a Help button to all
alert-boxes in an interactive session, wether it's Character Client (ChUI) or Graphical Client (GUI).
When the Help button is clicked, the ABL stack trace is displayed, along with a "Debug" button to start the Progress debugger.
This functionality may be useful in cases such as the following:
- Locating the source of error messages, such as: ** <file-name> record not on file. (138)
- Starting debugging at a certain point in an application. For example, a developer who uses SmartObjects might put a MESSAGE statement into a local version of a procedure or function to start debugging at that point.
Starting with OpenEdge 10.1x, this parameter also influences what is written to a client log file.
By default, if a client log is active (including .server.log for AppServer/WebSpeed) all error messages will be written to that log. If the -debugalert is active, the ABL stack trace will also be written to the log file, immediately after the error message.
This is useful for non-interactive clients, or for errors that are displayed in the status-area instead of in an alert-box. (Such as the default behavior for character client)
An alternative way to activate this behavior is to use the SESSION:DEBUG-ALERT attribute. This attribute can be set to TRUE to enable the feature, or to FALSE to disable it.