This is the mail archive of the
mailing list for the GCC project.
Re: ASAN test failures make compare_tests useless
- From: Manuel López-Ibáñez <lopezibanez at gmail dot com>
- To: Alexander Potapenko <glider at google dot com>
- Cc: Yury Gribov <y dot gribov at samsung dot com>, gcc Mailing List <gcc at gcc dot gnu dot org>, Konstantin Serebryany <konstantin dot s dot serebryany at gmail dot com>, Alexey Samsonov <samsonov at google dot com>, Dmitry Vyukov <dvyukov at google dot com>
- Date: Mon, 18 Aug 2014 17:17:53 +0200
- Subject: Re: ASAN test failures make compare_tests useless
- Authentication-results: sourceware.org; auth=none
- References: <CAESRpQBg3Rtxaxouap89HoKB+7d+F76HnnpcTTXCjY80mS981g at mail dot gmail dot com> <53F1925D dot 4050009 at samsung dot com> <53F19278 dot 3000503 at samsung dot com> <CAG_fn=Wqn4uAt4JqNM+qYGaGVLQHsfTC0whYwonnSAz_8yi-iA at mail dot gmail dot com>
On 18 August 2014 16:34, Alexander Potapenko <email@example.com> wrote:
> Not sure I understand what the problem is. Responded inline.
> On Mon, Aug 18, 2014 at 9:43 AM, Yury Gribov <firstname.lastname@example.org> wrote:
>> On 08/18/2014 09:42 AM, Yury Gribov wrote:
>>> On 08/16/2014 04:37 AM, Manuel López-Ibáñez wrote:
>>>> On the compile farm, ASAN tests seem to fail a lot like:
>>>> FAIL: c-c++-common/asan/global-overflow-1.c -O0 output pattern
>>>> test, is ==31166==ERROR: AddressSanitizer failed to allocate
>>>> 0xdfff0001000 (15392894357504) bytes at address 2008fff7000 (errno:
>>>> ==31166==ReserveShadowMemoryRange failed while trying to map
>>>> 0xdfff0001000 bytes. Perhaps you're using ulimit -v
>>>> , should match READ of size 1 at 0x[0-9a-f]+ thread T0.*(
> Sounds like the tests do not even start up properly. No mmap failures
> should be reported.
>>>> The problem is that those addresses and sizes are very random,
> The output pattern that must be printed has these addresses masked out
> (note "0x[0-9a-f]+" in your report).
> No other lines with varying addresses should be printed.
For the record, I think the fault lies in the GCC testing
infrastructure and not in ASAN. It is wrong to print as the test error
message the output of ASAN. It should print
FAIL: c-c++-common/asan/global-overflow-1.c -O0 output pattern
test, is ERROR
This is enough to see that something failed. For details one can go to
the detailed logs. But I didn't add the asan testing infrastructure
and I couldn't figure out how to fix this.