Package: gcc-4.9 Version: 4.9.2-10 Severity: normal When I tried building gcc from sources (debuild -us -uc), I got a number of errors like this:
FAIL: g++.dg/asan/interception-malloc-test-1.C -O1 output pattern test, is ==25380==ERROR: AddressSanitizer failed to allocate 0xdfff0001000 (15392894357504) bytes at address 0x02008fff7000 (12) ==25380==ReserveShadowMemoryRange failed while trying to map 0xdfff0001000 bytes. Perhaps you're using ulimit -v , should match malloc call.*( | )[^ ]*heap-use-after-free In fact I wasn't using ulimit -v, but I had turned off memory overcommitting (sysctl: vm.overcommit_memory=2). Obviously I have less than 14 TB of RAM in my system. ;) After I turned it on, these errors disappeared. So I suggest: - If possible, amend the test to use a more reasonable allocation. Not sure what it's actually testing, but I wonder what I can do with 14 TB (which is way short of the 64 bit address range) that it couldn't do with, say 6 GB (larger than 32 bit range, in case that matters). Otherwise: - In the wording of the message, add "or have turned off memory overcommitting" as a possible reason. - Verify [ `sysctl -n vm.overcommit_memory` -eq 0 ] early in the build process, so you don't get to see such errors after a long time building. Same for a ulimit check if there isn't one already. -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1yscwl-0007s1...@goedel.fjf.gnu.de
