Provides a list of issues commonly reported in a PLIDUMP and provides common solutions.
- No symbol information present
- This usually occurs when the code was not compiled for debugging.
Solution: Compile the code using the
-deb option.
- .STB file not found
- The directory containing the
.dll or
.so file is first checked for a corresponding
.stb file. The problem occurs when the
.stb file is not found in the current directory or in a directory on list defined by the CODEWATCH_STBPATH environment variable.
Solution: Copy the appropriate
.stb file into the current directory, or add the path to this file to the CODEWATCH_STBPATH environment variable.
- .STB file out of date
- A PLIDUMP can be truncated or even cause an abend within the application if the
.stb files that are found are not correct for the object code compiled and linked into the corresponding
.dll or
.so file.
Solution: Ensure that the
.stb and
.dll or
.so correspond correctly to one another.
- The code on the line number cited in an entry on the call stack actually occurs on a line number later in the program code
- This is expected behavior in most cases as the PC is pointing at the "next line" at the time of the abend.
- Compile listing is out of date
- This can happen when attempting to equate reported line numbers with actual lines of code.
Note: See also
Annotation of a Simple PLIDUMP.