Your message dated Wed, 30 Dec 2009 14:21:55 +0100
with message-id <4b3b53f3.7050...@debian.org>
and subject line Re: Bug#541300: gcc: 'CXXFLAGS="-g -ggdb -O0" debuild -us -uc'
runs out of memory
has caused the Debian Bug report #541300,
regarding gcc: 'CXXFLAGS="-g -ggdb -O0" debuild -us -uc' runs out of memory
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.)
--
541300: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541300
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc
Version: 4:4.3.2-2
Severity: normal
I will attach the output I captured using this command
CXXFLAGS="-g -ggdb -O0" nice -n 10 debuild -us -uc 2>&1 | tee make.txt
I'm no gcc build expert, so someone should take a look at this.
WARNING: program timed out.
FAIL: gcc.c-torture/compile/limits-blockid.c -O0 (test for excess errors)
I gave it the nice priority as the build used both of my CPU's (Pentium dual
core) and I wanted to
continue using the laptop.
When the above error occurred my machine became unresponsive - caps-lock and
num-lock lights
didn't respond when the corresponding keys were pressed.
Even the mouse cursor stopped moving.
Just as I was about to hard-reboot the machine things started coming back to
life.
I was able to start system guard.
There was a process ("cc1" I think - I forgot to note the exact program name)
using
2,800,000 VmRss.
I've got 3GB of memory so if VmRss is measured in KBytes then that's about
2.8GB.
# cat /proc/swaps
Filename Type Size Used Priority
/dev/mapper/VgCompaq-swap partition 2928632 0 -1
The entire build took about 4:30 hours.
-- System Information:
Debian Release: 5.0.2
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages gcc depends on:
ii cpp 4:4.3.2-2 The GNU C preprocessor (cpp)
ii gcc-4.3 4.3.2-1.1 The GNU C compiler
Versions of packages gcc recommends:
ii libc6-dev [libc-dev] 2.7-18 GNU C Library: Development Librari
Versions of packages gcc suggests:
ii autoconf 2.61-8 automatic configure script builder
ii automake1.9 1.9.6+nogfdl-3 A tool for generating GNU Standard
ii bison 1:2.3.dfsg-5 A parser generator that is compati
ii flex 2.5.35-6 A fast lexical analyzer generator.
pn gcc-doc <none> (no description available)
ii gcc-multilib 4:4.3.2-2 The GNU C compiler (multilib files
ii gdb 6.8-3 The GNU Debugger
ii libtool 1.5.26-4 Generic library support script
ii make 3.81-5 The GNU version of the "make" util
pn manpages-dev <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
closing the report; running the testsuite requires some resources. This
behaviour is expected. Setting DEB_BUILD_OPTIONS=nocheck doesn't run the
testsuite and the package should build ok.
On 13.08.2009 08:52, Philip Ashmore wrote:
Package: gcc
Version: 4:4.3.2-2
Severity: normal
I will attach the output I captured using this command
CXXFLAGS="-g -ggdb -O0" nice -n 10 debuild -us -uc 2>&1 | tee make.txt
I'm no gcc build expert, so someone should take a look at this.
WARNING: program timed out.
FAIL: gcc.c-torture/compile/limits-blockid.c -O0 (test for excess errors)
I gave it the nice priority as the build used both of my CPU's (Pentium dual
core) and I wanted to
continue using the laptop.
When the above error occurred my machine became unresponsive - caps-lock and
num-lock lights
didn't respond when the corresponding keys were pressed.
Even the mouse cursor stopped moving.
Just as I was about to hard-reboot the machine things started coming back to
life.
I was able to start system guard.
There was a process ("cc1" I think - I forgot to note the exact program name)
using
2,800,000 VmRss.
I've got 3GB of memory so if VmRss is measured in KBytes then that's about
2.8GB.
--- End Message ---
