Skip to content
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

Bug Hash derived from report when it should be from event #4402

Open
jstevens176 opened this issue Dec 9, 2024 · 0 comments
Open

Bug Hash derived from report when it should be from event #4402

jstevens176 opened this issue Dec 9, 2024 · 0 comments

Comments

@jstevens176
Copy link

jstevens176 commented Dec 9, 2024

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.

  1. Run command '...'
  2. Go to '...'
  3. Click on '....'
  4. Scroll down to '....'
  5. 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant