Traceback identifies and describes statements in the source code that contribute to issues. Traceback lines link directly to the source code and follow execution order.
You can click the traceback statements to navigate through your source code to find problems that led to the issue you are viewing in the list. Key statements that contribute to issues are marked with red rectangles and include a description of the problem.
A plus-sign to the left of a traceback statement indicates an associated call stack. You can expand the tree to navigate traceback details.
Traceback may not be available for all issues. If you don't see any traceback for the error selected from the list of issues, it means that the problem associated with the issue is confined to one line of code.
Connected desktop analysis: Interprocedural issues are indicated by a plus sign. With connected desktop, interprocedural issues that span multiple functions and methods have the added benefit of a full-context analysis.
With connected desktop, Klocwork analyzes the developer's code, but with a full understanding of dependencies on the rest of the system. This gives developers the power of a centralized system analysis before code check-in.
The traceback feature indicates dependencies outside the developer context with <lib> or library references in its traceback lines.
Note: If the detected issue or traceback line is located in a file outside your context (that is, the source code that contains this function was not available to the Klocwork build), then the corresponding source file cannot be opened.