Your message dated Tue, 20 Sep 2016 22:15:11 +0000 with message-id <[🔎] E1bmTJn-0005QY-0D@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 owner@bugs.debian.org immediately.) -- 785249: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785249 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: gcc-4.9: test suite errors when memory overcommitting is turned off
- From: Frank Heckenbach <f.heckenbach@fh-soft.de>
- Date: Wed, 13 May 2015 22:07:37 +0200
- Message-id: <E1YscwL-0007S1-L6@goedel.fjf.gnu.de>
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 ---
- To: 450746-done@bugs.debian.org,727621-done@bugs.debian.org,734973-done@bugs.debian.org,748024-done@bugs.debian.org,751812-done@bugs.debian.org,753134-done@bugs.debian.org,755295-done@bugs.debian.org,756945-done@bugs.debian.org,759683-done@bugs.debian.org,759870-done@bugs.debian.org,762005-done@bugs.debian.org,762238-done@bugs.debian.org,762640-done@bugs.debian.org,764195-done@bugs.debian.org,764280-done@bugs.debian.org,764624-done@bugs.debian.org,764732-done@bugs.debian.org,766840-done@bugs.debian.org,768265-done@bugs.debian.org,772436-done@bugs.debian.org,773065-done@bugs.debian.org,774541-done@bugs.debian.org,774543-done@bugs.debian.org,774548-done@bugs.debian.org,777169-done@bugs.debian.org,777275-done@bugs.debian.org,781060-done@bugs.debian.org,782391-done@bugs.debian.org,784544-done@bugs.debian.org,785249-done@bugs.debian.org,785762-done@bugs.debian.org,786883-done@bugs.debian.org,797151-done@bugs.debian.org,797426-done@bugs.debian.org,798029-done@bugs.debian.org,799953-done@bu gs.debian.org,805616-done@bugs.debian.org,810868-done@bugs.debian.org,814239-done@bugs.debian.org,816776-done@bugs.debian.org,823222-done@bugs.debian.org,
- Cc: gcc-4.9@packages.debian.org, gcc-4.9@packages.qa.debian.org
- Subject: Bug#838316: Removed package(s) from unstable
- From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
- Date: Tue, 20 Sep 2016 22:15:11 +0000
- Message-id: <[🔎] E1bmTJn-0005QY-0D@franck.debian.org>
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 ftpmaster@ftp-master.debian.org. Debian distribution maintenance software pp. Chris Lamb (the ftpmaster behind the curtain)
--- End Message ---