UndefinedBehaviorSanitizer failed to deallocate

[Martin Sebor]

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. For more on test case
reduction see the following Wiki page:

   http://gcc.gnu.org/wiki/A_guide_to_testcase_reduction

If you're up to some debugging, you might want to see what
the strace or ltrace output is for the failing invocation (i.e.,
make sure the arguments to the call match the arguments to the
mmap call, if [sl]trace shows them). You could also do a search
in the LLVM compiler-rt bug tracking database or clang mailing
list archives for references to the same error to see if it has
been discussed there.

Martin