-
Notifications
You must be signed in to change notification settings - Fork 376
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
report-converter [INFO] No 'lsan' results can be found #4280
Comments
Some analyzer tools (e.g. sanitizers) give an output that contains relative source file paths. When report-converter is executed from a directory where these absolute paths are not valid, then reports are simply not generated. If all reports contain such a relative path, then this message is given by report-converter: No 'lsan' results can be found in '...' This message is obviously false. This patch allows non-existing file paths in the analyzer outputs. Using further CodeChecker commands (store, parse, etc.) will emit an error message on these paths anyway, but at least we get rid of the incomprehensible error message above. Fixes Ericsson#4280
Hi, Make sure that |
Sorry, closed accidentally. I didn't mean to close it until the patch is merged. |
Oh, thanks for letting me know. I wasn't aware that the |
Actually, |
Describe the bug
report-converter is saying "No 'lsan' results can be found" when there clearly is a leak detected and in the file
CodeChecker version
To Reproduce
Steps to reproduce the behaviour:
report-converter -t lsan -o report ./test.out
[INFO] - No 'lsan' results can be found in '...'
Expected behaviour
report-converter found a leak
Desktop (please complete the following information)
The text was updated successfully, but these errors were encountered: