Your message dated Tue, 20 Sep 2016 22:15:11 +0000
with message-id <e1bmtjn-0005qy...@franck.debian.org>
and subject line Bug#838316: Removed package(s) from unstable
has caused the Debian Bug report #785249,
regarding gcc-4.9: test suite errors when memory overcommitting is turned off
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
785249: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785249
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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.
--- End Message ---
--- Begin Message ---
Version: 4.9.4-2+rm
Dear submitter,
as the package gcc-4.9 has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/838316
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)
--- End Message ---
