I rebuild the package without optimizations got some more data. The ASAN
out now matches the gdb one
READ of size 9 at 0x6040001944b8 thread T0
#0 0x14454c2 in __interceptor_strndup
/opt/media/clang_nightly/llvm/utils/release/final/llvm.src/projects/compiler-rt/lib/asan/../sanitizer_common/sa
Sorry I didn't think about this before, but I gave the non-ASAN version
of the application a spin with valgrind 3.13 and it doesn't report any
memory errors with it - so it's possible this is either something
valgrind won't catch or a false positive by ASAN.
--
You received this bug notification
Public bug reported:
I am running an application which has a feature which utilizes Qt5. For testing
purposes this application was built with the AddressSanitizer of the official
clang 5.0.1 binariesfor ubuntu 16.04. This was working fine until a few days
ago. It started out with another user r
Public bug reported:
When compiling a program with clang and MemorySanitizer you get the
following:
Uninitialized bytes in __interceptor_strcmp at offset 0 inside [0x6080ded8,
2)
==10413== WARNING: MemorySanitizer: use-of-uninitialized-value
#0 0x7fdfc0c6575d in QMetaType::registerType(
