Kbase 19455: ABL Debugging -debugalert Startup Parameter
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
09/09/2010 |
|
Status: Verified
GOAL:
Startup parameter -debugalert allows you to obtain a ABL stack trace for a Progress application at runtime.
GOAL:
-debugalert Startup Parameter
FACT(s) (Environment):
Progress 9.x
OpenEdge 10.x
FIX:
The -debugalert parameter adds a Help button to ALL alert-boxes. When you click on the button, the stack trace is displayed and you are given the option to start the Progress debugger (with a click on a "Debug" button).
An alternative way to get a stack trace is to use the SESSION:DEBUG-ALERT attribute. This attribute can be also used to switch the feature off. The functionality can help in situations such as:
- Finding where some error messages come from, such as:
** <file-name> record not on file. (138)
- A developer who uses SmartObjects can put a MESSAGE statement into a local version of the procedure/function to start debugging.
However, the use of the -debugalert session parameter can cause a help dialog box to appear behind the Progress window. It can only be accessed via Alt-Tab or by dragging the dialog-box out from underneath the window.
Follow these steps to recreate the problem:
1) Open the AppBuilder directly.
2) Connect to the Sports database.
3) Open a new procedure window.
4) Create a normal window and a browser.
5) In the query builder, select the "CHECK SYNTAX" button.
Notice that the alert-box appears behind the Query Builder window, and that the NEW PROCEDURE window appears to parent the dialogue-box.
Solution: Remove any reference to -debugalert from the Icon/Shortcut target properties, any startup file that is called for the AppBuilder, or set SESSION:DEBUG-ALERT = FALSE.