Kbase P24788: How to generate a readable Progress Protrace file on Windows
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
02/05/2005 |
|
Status: Verified
GOAL:
How to generate a readable Progress Protrace file on Windows
GOAL:
How to generate a readable stack trace on Windows systems that do not generate Dr Watson log files
GOAL:
How to generate a readable stack trace on Windows
GOAL:
How to enable Progress to resolve function names in a stack trace on Windows
GOAL:
How to obtain a readable stack trace by resolving function names in a Protrace file
FACT(s) (Environment):
Progress 8.3x
Progress 9.x
OpenEdge 10.x
Windows
Windows XP
Windows 2003
FIX:
On occasion, when a 4GL application crashes the resulting Protrace file will only contain the name of a Progress .DLL file rather than the name of the functions called up to the point of the failure.
In order to resolve function names and produce a readable Protrace file, the Protrace facility needs to have the DLC\bin folder in the system Path:
Option #1 - Add the location of the DLC\Bin folder to the system Path
Go to Control Panel > select System > select the Advanced tab > select the Environment Variables button.
Locate the Path variable in System variables.
Double-click on the Path variable and add DLC\Bin to the end of the string.
Restart any Progress processes to take into account the change to the Path.
Option #2 - Start Progress via ProEnv
Start ProEnv which will automatically set the locations of DLC and DLC\Bin.
Start Progress using the command line used to start the 4GL application i.e.
PROWIN32 -db sports2000 -S <Service> -H <HostName> -p <StartProcedure>