Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Report hashes are different for the very same report

See original GitHub issue

Steps to reproduce:

Ubuntu 16.04, boost 1.65
CodeChecker analyze the project at https://github.com/martong/graphisoft_competition_2017

[HIGH] stl_uninitialized.h:83:19: Forming reference to null pointer [core.NonNullParamChecker]
    std::_Construct(std::__addressof(*__cur), *__first);
                    ^
  ReportHash: b378379a1773641e430c27a0cad9d1c6
  Steps:
    1, vector.tcc:429:4: Null pointer value stored to '__new_finish'
    2, vector.tcc:434:7: Passing null pointer value via 3rd parameter '__result'
    3, vector.tcc:432:8: Calling '__uninitialized_move_if_noexcept_a'
    4, stl_uninitialized.h:304:5: Entered call from 'vector::_M_realloc_insert'
    5, stl_uninitialized.h:312:52: Passing null pointer value via 3rd parameter '__result'
    6, stl_uninitialized.h:310:14: Calling '__uninitialized_copy_a'
    7, stl_uninitialized.h:286:5: Entered call from '__uninitialized_move_if_noexcept_a'
    8, stl_uninitialized.h:289:55: Passing null pointer value via 3rd parameter '__result'
    9, stl_uninitialized.h:289:14: Calling 'uninitialized_copy'
    10, stl_uninitialized.h:114:5: Entered call from '__uninitialized_copy_a'
    11, stl_uninitialized.h:134:33: Passing null pointer value via 3rd parameter '__result'
    12, stl_uninitialized.h:131:14: Calling '__uninitialized_copy::__uninit_copy'
    13, stl_uninitialized.h:75:9: Entered call from 'uninitialized_copy'
    14, stl_uninitialized.h:79:4: '__cur' initialized to a null pointer value
    15, stl_uninitialized.h:82:15: Entering loop body
    16, stl_uninitialized.h:83:19: Forming reference to null pointer
--
[HIGH] stl_uninitialized.h:83:19: Forming reference to null pointer [core.NonNullParamChecker]
    std::_Construct(std::__addressof(*__cur), *__first);
                    ^
  ReportHash: 072e5edbba314a5bdd1babd3e293defa
  Steps:
    1, vector.tcc:429:4: Null pointer value stored to '__new_finish'
    2, vector.tcc:434:7: Passing null pointer value via 3rd parameter '__result'
    3, vector.tcc:432:8: Calling '__uninitialized_move_if_noexcept_a'
    4, stl_uninitialized.h:304:5: Entered call from 'vector::_M_realloc_insert'
    5, stl_uninitialized.h:312:52: Passing null pointer value via 3rd parameter '__result'
    6, stl_uninitialized.h:310:14: Calling '__uninitialized_copy_a'
    7, stl_uninitialized.h:286:5: Entered call from '__uninitialized_move_if_noexcept_a'
    8, stl_uninitialized.h:289:55: Passing null pointer value via 3rd parameter '__result'
    9, stl_uninitialized.h:289:14: Calling 'uninitialized_copy'
    10, stl_uninitialized.h:114:5: Entered call from '__uninitialized_copy_a'
    11, stl_uninitialized.h:134:33: Passing null pointer value via 3rd parameter '__result'
    12, stl_uninitialized.h:131:14: Calling '__uninitialized_copy::__uninit_copy'
    13, stl_uninitialized.h:75:9: Entered call from 'uninitialized_copy'
    14, stl_uninitialized.h:79:4: '__cur' initialized to a null pointer value
    15, stl_uninitialized.h:82:15: Entering loop body
    16, stl_uninitialized.h:83:19: Forming reference to null pointer

Issue Analytics

State:
Created 6 years ago
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

gyorbcommented, Oct 9, 2017

I think this should be handled better in the clang static analyzer. In CodeChecker the base of the comparison is the bug hash and the path comes only after it. At the UI there is the similar bugs option (same hash multiple path) or uniqueing where the bug hash is used to find the unique reports.

0reactions

martongcommented, Nov 7, 2017

Fixed in Clang: https://reviews.llvm.org/D38728

Top Results From Across the Web

Using file hashes to prove two models are the same - Numeritas

I say 'nearly' unique because it is possible for two different files to have identical hashes. This is known as a 'collision'. The...

How to determine the unique hash of a file detected by ...

Please note: Using the hashes seen in this report are a very crude method for determining if the same variant is being seen...

Full article: CD-R Acquisition Hashes Affected by Write Options

The results suggested that certain write options cause hash applications to report different hashes. We conclude with a discussion of possible consequences of ......

Why Hash Values Are Crucial in Evidence Collection & Digital ...

As long as a piece of evidence was correctly collected and processed, any other party independently examining the hash value will find the...

NCCIC ICS Fact Sheet - File Hashing - CISA

... other similar services allow one to submit files and URLs for inspection for malicious content and look up URLs and hashes to...