The file indexing in -plist-output output (used for formatting results in CodeChecker-friendly way) is sometimes set to 0, because the code reported the error didn't provide info about the indexing.
For example, I get in the errors of ctunullpointer but inspecting the .plist file you see that the file index is set to 0, which results with CodeChecker not pointing to the right file on the stack call view of it.
Here is a not-too-ugly patch I used locally (i.e. store in a static variable the input file list, and search for that on error outputting). Anything better that you can suggest?
I need to write some tests for the ctu* checks "soon" and will include this use case. I will file an upstream ticket when I have a failing test case. Quite possible there are some other tests which should be extended as well.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The file indexing in
-plist-output
output (used for formatting results in CodeChecker-friendly way) is sometimes set to 0, because the code reported the error didn't provide info about the indexing.For example, I get in the errors of
ctunullpointer
but inspecting the.plist
file you see that the file index is set to 0, which results with CodeChecker not pointing to the right file on the stack call view of it.Here is a not-too-ugly patch I used locally (i.e. store in a static variable the input file list, and search for that on error outputting). Anything better that you can suggest?
Thanks for your report.
I need to write some tests for the
ctu*
checks "soon" and will include this use case. I will file an upstream ticket when I have a failing test case. Quite possible there are some other tests which should be extended as well.