This is the mail archive of the
mailing list for the GCC project.
Re: Testing Leak Sanitizer?
- From: Konstantin Serebryany <konstantin dot s dot serebryany at gmail dot com>
- To: Yury Gribov <y dot gribov at samsung dot com>
- Cc: Christophe Lyon <christophe dot lyon at linaro dot org>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Tue, 30 Sep 2014 10:08:43 -0700
- Subject: Re: Testing Leak Sanitizer?
- Authentication-results: sourceware.org; auth=none
- References: <CAKdteOYC2vnNZb8ivbFCeX4AGeVdxd5Z9FaMv+DeGSLo_H3RCw at mail dot gmail dot com> <542ADEB5 dot 8050603 at samsung dot com>
Correct, you can run tests from llvm tree with any compiler.
Note that lsan does not depend on the compiler, it is a library-only feature.
On Tue, Sep 30, 2014 at 9:47 AM, Yury Gribov <firstname.lastname@example.org> wrote:
> On 09/30/2014 07:15 PM, Christophe Lyon wrote:
>> After I've recently enabled Address Sanitizer for AArch64 in GCC, I'd
>> like to enable Leak Sanitizer.
>> I'd like to know what are the requirements wrt testing it? IIUC there
>> are no lsan tests in the GCC testsuite so far.
>> Should I just test a few sample programs to check if basic functionality
>> is OK?
>> The patch seems to be a 1-line patch, I just want to check the
>> acceptance criteria.
> AFAIK compiler-rt testsuite supports running under non-Clang compiler. Don't
> ask me how to setup the beast though.