You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When creating path sensitive bug hashes using the report converter the bug hash is always derived from the top level report file instead of following the correct bug path and picking the correct line from each file. This resulted in hashes that didn't correspond to the bug that they were supposedly derived from, and increased the risk of hash collision
CodeChecker version
You can get version info by running CodeChecker version.
6.25
To Reproduce
Steps to reproduce the behaviour:
Generate bug hashes from bug paths that go via multiple files. You will most likely get a hash collision when the top level report.file is the same and the bug occurs at the same line number, but in different event.files.
Run command '...'
Go to '...'
Click on '....'
Scroll down to '....'
See error
Expected behaviour
What you expected to happen.
Desktop (please complete the following information)
OS: Linux
Browser: NA this bug occurs in the backend
Version: 6.25
Additional context
The fix is described here: #4403
The text was updated successfully, but these errors were encountered:
Describe the bug
When creating path sensitive bug hashes using the report converter the bug hash is always derived from the top level report file instead of following the correct bug path and picking the correct line from each file. This resulted in hashes that didn't correspond to the bug that they were supposedly derived from, and increased the risk of hash collision
CodeChecker version
You can get version info by running
CodeChecker version
.6.25
To Reproduce
Steps to reproduce the behaviour:
Generate bug hashes from bug paths that go via multiple files. You will most likely get a hash collision when the top level report.file is the same and the bug occurs at the same line number, but in different event.files.
Expected behaviour
What you expected to happen.
Desktop (please complete the following information)
Additional context
The fix is described here: #4403
The text was updated successfully, but these errors were encountered: