Container-overflow false positive with uninstrumented code

[GoogleCodeExporter]

Imagine two modules, both using std::vector, only one of them is instrumented. 
Push_back from the non-instrumented module will not unpoison the memory for the 
newly added element. Access from the instrumented module will trigger a false 
report.

Note that these two modules don't need to share a common instance of 
std::vector. Theoretically, it is possible for the linker to choose the 
uninstrumented version of std::vector::push_back (if it was not inlined) to be 
called from the instrumented module.

Original issue reported on code.google.com by euge...@google.com on 8 Dec 2014 at 9:26

[GoogleCodeExporter]

Adding Project:AddressSanitizer as part of GitHub migration.

Original comment by ramosian.glider@gmail.com on 30 Jul 2015 at 9:06

• Added labels: ProjectAddressSanitizer