llvm clang

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

llvm clang

Rick Leir
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



------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
_______________________________________________
Valgrind-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
Reply | Threaded
Open this post in threaded view
|

Re: llvm clang

Philippe Waroquiers
In general, there should be no problem to use Valgrind on
code/executable produced by clang (or whatever other compiler).

Yes, the problem below seems to be related to the fact that you are
using at the same time valgrind and ASan.
If you want to use valgrind, then you should compile without ASan.
And if you want to use ASan, then you should not use valgrind on ASan
compiled code.

Philippe


On Thu, 2016-06-23 at 14:36 -0400, Rick Leir wrote:

> 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
>
>
> ------------------------------------------------------------------------------
> Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
> Francisco, CA to explore cutting-edge tech and listen to tech luminaries
> present their vision of the future. This family event has something for
> everyone, including kids. Get more information and register today.
> http://sdm.link/attshape
> _______________________________________________ Valgrind-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/valgrind-users



------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
_______________________________________________
Valgrind-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/valgrind-users