Kbase P22254: Error 2999 occurs when starting Debugger with DEBUGGER:DEBUG() statement
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  11/10/2009 |
|
Status: Verified
SYMPTOM(s):
Error 2999 occurs when starting Debugger with DEBUGGER:DEBUG() statement
Error 2999 is generated when using any debugger commands (Step Into, Step Over, etc.)
Nothing to execute. (2999)
Unable to debug code further
Debugger has to be closed in order to continue
FACT(s) (Environment):
Starting the Debugger with DEBUGGER:DEBUG()
Affects pre-9.1D05 debugger
Affects new debugger introduced in 9.1D05
Error 2999 is intended to inform the user that there is no code running in the debugger
Affects code with/without UI
Progress 9.X
OpenEdge 10.x
Windows
CAUSE:
This is expected behavior because DEBUGGER:DEBUG() starts the debugger in stand-alone mode, as documented.
The procedure that executes DEBUGGER:DEBUG() is suspended; a new procedure must be loaded into the debugger and Debug/Run selected to execute the loaded procedure. When the procedure is complete, the original procedure (the one which executed DEBUGGER:DEBUG) is resumed.
FIX:
Option #1
Start the debugger before running the procedure that needs debugging. Use the DEBUGGER:SET-BREAK() and specify appropriate line number to invoke the debugger at the desired point
Option #2
Use the following statements to launch and involve the debugger at a specific point:
DEBUGGER:INITIATE().
DEBUGGER:SET-BREAK().