On 04/11/2015 04:29, Martin Sebor wrote:
> On 10/24/2015 07:47 AM, Alex Markin wrote:
>> Hello.
>>
>> I don't know how to report this bug, but I have the following
>> situation. I compile my program with "-fsanitize=undefined". My
>> program is a compiler. After that I start compiling the 465.tonto
>> SPEC. And while compiling it I get the following error:
>>
>> ==19735==ERROR: UndefinedBehaviorSanitizer failed to deallocate
>> 0x100000 (1048576) bytes at address 0x7f25c1b00000
>> ==19735==Sanitizer CHECK failed:
>> ../../../../src/libsanitizer/sanitizer_common/sanitizer_posix.cc:133
>> (("unable to unmap" && 0)) != (0) (0, 0)
>>
>> My gcc is:
>>
>> x86_64-none-linux-gcc --version
>> x86_64-none-linux-gcc (GCC) 6.0.0 20151018 (experimental)
>> Copyright (C) 2015 Free Software Foundation, Inc.
>> This is free software; see the source for copying conditions. There is NO
>> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>>
>> my system is:
>>
>> $ uname -a
>> Linux ubuntu64 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt9-3~deb8u1
>> (2015-04-24) x86_64 GNU/Linux
>>
>> This bug is reproducable with stable gcc-5 on debian system. To my
>> pity I can't give you the binary or source of my compiler, but I can
>> try to get information you need to fix this bug
>
> Unless this is a known problem (my Bugzilla search for the strings
> mentioned above didn't turn up anything), the information needed
> to fix the problem is a standalone test case that reproduces it.
> The full source code of your project isn't necessary (or even
> desirable), just a test case reduced from the translation unit
> on which GCC aborts with the error above.
Martin,
I believe you misread Alex's message.
It's not gcc which aborts. It's the binary produced by gcc.
IIUC, he has src.c which he compiles with
gcc -fsanitize=undefined [other options?] src.c
And then ./a.out [argument list] errors out in libsanitizer.
The problem seems to be in libsanitizer.
Creating an appropriate test-case might be tricky.
Regards.
