|
|
Boost Testing : |
Subject: Re: [Boost-testing] BenPope x86_64 runners + runner requirements
From: Raffi Enficiaud (raffi.enficiaud_at_[hidden])
Date: 2015-03-22 05:08:12
Le 21/03/15 11:35, Ben Pope a écrit :
> On Saturday, March 21, 2015 10:42 AM, Ben Pope wrote:
>> On Saturday, March 21, 2015 12:00 AM, Raffi Enficiaud wrote:
>>> Hi,
>>>
>>> I would like to know if these runners are actually being able to compile
>>> anything (lack of cstddef).
>>
>> Yeah, sorry about that, I'll look into it today.
>
> OK, it's working now. Also, for msan and tsan, I've set the rpath to
> use the sanitized libc++, which has reduced the number of warnings
> produced.
>
> I've just kicked off a full build.
>
> Ben
Thanks, the run has cycled and almost everything is green for this runner :)
I have
=================================================================
==9511==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 171 byte(s) in 9 object(s) allocated from:
#0 0x4c5695 in realloc
/home/development/llvm/3.6.0/final/llvm.src/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:61:3
#1 0x7f339dfc3682 in __cxa_demangle
(/usr/local/lib/libc++abi.so.1+0x8682)
SUMMARY: AddressSanitizer: 171 byte(s) leaked in 9 allocation(s).
EXIT STATUS: 23
=================================================================
Only for clang-linux-3.6~asan~c14_libc++. This would be a demangling
that should be freed:
https://gcc.gnu.org/onlinedocs/libstdc++/manual/ext_demangling.html
Just wondering why this is not happening in other compiler versions of
this runner.
Is the memory leak detection active for all compilers?
Thanks for having fixed this,
Raffi