|
From: Rick L. <rl...@le...> - 2016-06-23 18:55:46
|
Hi all, Is it appropriate to compile with LLVM/Clang then debug with Valgrind? Linux 64 bit, Ubuntu. I selected the clang options in the following: $ sudo update-alternatives --config c++ $ sudo update-alternatives --config cc This was configured automatically when I installed clang: # ldconfig -p |grep cla libclang-3.8.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libclang-3.8.so.1 To run Valgrind: $ valgrind -v --trace-children=yes --gen-suppressions=yes --leak-check=full ./fuzz/cert -max_len=3072 -jobs=32 -workers=32 ../fuzz/cert_corpus/ ... --13429-- Reading syms from /lib/x86_64-linux-gnu/libc-2.23.so --13429-- Considering /lib/x86_64-linux-gnu/libc-2.23.so .. --13429-- .. CRC mismatch (computed 2adb2e50 wanted 9b73f606) --13429-- Considering /usr/lib/debug/lib/x86_64-linux-gnu/libc-2.23.so .. --13429-- .. CRC is valid ... ==13429==Shadow memory range interleaves with an existing memory mapping. ASan cannot proceed correctly. ABORTING. ==13429==ASan shadow was supposed to be located in the [0x00007fff7000-0x10007fff7fff] range. ==13429==Process memory map follows: ... Does it matter that the symbols are read above from libc not libclang? Maybe I just need to disable clang's AddressSanitizer I did a quick search, and found a few mentions on Stackoverflow, but nothing to answer this. Thanks -- Rick |