A protrace files (also called stack trace) is a report generated to aid in debugging by showing where exactly an error occurs.
- A protrace file is generated from a core file.
- A core file is generated by an error in a Progress executable.
- A protrace file is a stack trace from a Progress session that had a serious error.
- The protrace file is created from a core file being 'unwound' by an operating system utility such as the Linux backtrace.
- The last few stack frames often indicate the origin of the problem or the bug. For further information refer to Article:
How to interpret a protrace
The format for a protrace file is:
protrace.<PID>.
PASOE AppServer agent is: protrace.
T<thread>.<pid>
The file is created in the directory where the failing process was started from, which is not always the OpenEdge default working directory and the process needs write permissions to that directory:
On Windows it is necessary to have the pdb files from the install media manually copied to the install directory (%DLC%):
Since OpenEdge 10.1C it is possible to manually generate a protrace file with proGetStack against an ABL Client Session. For further information refer to Article:
