Your message dated Mon, 20 Sep 2004 08:54:23 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#272231: possible g++ memory leakage
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 18 Sep 2004 15:03:17 +0000
>From [EMAIL PROTECTED] Sat Sep 18 08:03:17 2004
Return-path: <[EMAIL PROTECTED]>
Received: from civis.wigner.bme.hu [152.66.224.132] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1C8gk8-0004K0-00; Sat, 18 Sep 2004 08:03:17 -0700
Received: from carrier ([152.66.224.133] helo=localhost.localdomain)
by civis.wigner.bme.hu with esmtp (Exim 3.35 #1 (Debian))
id 1C8gls-0008Na-00
for <[EMAIL PROTECTED]>; Sat, 18 Sep 2004 17:05:04 +0200
Received: from lorro by localhost.localdomain with local (Exim 4.34)
id 1C8gkQ-0005nx-LO
for [EMAIL PROTECTED]; Sat, 18 Sep 2004 17:03:34 +0200
Date: Sat, 18 Sep 2004 17:03:34 +0200
To: [EMAIL PROTECTED]
Subject: possible g++ memory leakage
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.6+20040722i
From: [EMAIL PROTECTED]
X-Scanner: exiscan *1C8gls-0008Na-00*ktXnQXn5eb2* (Wigner Jeno Kollegium)
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.4 required=4.0 tests=BAYES_00,HAS_PACKAGE,
NO_REAL_NAME autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
Package: g++
Version: 3.3.4-2
Severity: important
When building the latest (0.16) mythtv with apt-build,
at file globalsettings.cpp g++ slowly eats up all the
memory the machine has (no matter how much), then dies
with inertal error (probably gets oomkilled).
Reproducing the error: (Debian unstable, as of 2004-09-18)
1., Add (if not already there) to /etc/apt/sources.list :
deb http://dijkstra.csh.rit.edu/~mdz/debian unstable mythtv
2., Install (if you don't yet have it) apt-build :
apt-get install apt-build && apt-get update
3., Set -O3 -march=k6-3 -mcpu=k6-3 (probably optional) in
/etc/apt/apt-build.conf
4., Install mythtv with apt-build :
apt-build install
5., Wait...
The error will appear when globalsettings.cpp gets compiled.
(Takes quite long) You can start a "watch free" to see
the memory leakage.
Kernel: Linux 2.6.5 official source
Lorand Szollosi <[EMAIL PROTECTED]>
-lorro
---------------------------------------
Received: (at 272231-done) by bugs.debian.org; 20 Sep 2004 06:54:27 +0000
>From [EMAIL PROTECTED] Sun Sep 19 23:54:27 2004
Return-path: <[EMAIL PROTECTED]>
Received: from mail.cs.tu-berlin.de [130.149.17.13] (root)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1C9I4A-0000Kg-00; Sun, 19 Sep 2004 23:54:27 -0700
Received: from mailhost.cs.tu-berlin.de ([EMAIL PROTECTED] [130.149.17.13])
by mail.cs.tu-berlin.de (8.9.3p2/8.9.3) with ESMTP id IAA29871;
Mon, 20 Sep 2004 08:54:24 +0200 (MEST)
Received: from localhost (localhost [127.0.0.1])
by mailhost.cs.tu-berlin.de (Postfix) with ESMTP id 43495F212;
Mon, 20 Sep 2004 08:54:24 +0200 (MEST)
Received: from mailhost.cs.tu-berlin.de ([127.0.0.1])
by localhost (bueno [127.0.0.1]) (amavisd-new, port 10224) with ESMTP
id 21883-06; Mon, 20 Sep 2004 08:54:24 +0200 (MEST)
Received: from bolero.cs.tu-berlin.de (bolero.cs.tu-berlin.de [130.149.19.1])
by mailhost.cs.tu-berlin.de (Postfix) with ESMTP;
Mon, 20 Sep 2004 08:54:23 +0200 (MEST)
Received: (from [EMAIL PROTECTED])
by bolero.cs.tu-berlin.de (8.12.10+Sun/8.12.8/Submit) id i8K6sN8A009577;
Mon, 20 Sep 2004 08:54:23 +0200 (MEST)
From: Matthias Klose <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <[EMAIL PROTECTED]>
Date: Mon, 20 Sep 2004 08:54:23 +0200
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: Bug#272231: possible g++ memory leakage
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
X-Mailer: VM 7.03 under 21.4 (patch 6) "Common Lisp" XEmacs Lucid
X-Virus-Scanned: by amavisd-new at cs.tu-berlin.de
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.5 required=4.0 tests=BAYES_30,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
[EMAIL PROTECTED] writes:
> > the file compiles fine, although the peak memory usage is at about
> > 460MB. please add more swap space and retry.
> Sorry, you are rigth. After adding another 600MB swap the
> compile went fine. So the 'bug' is resolved.
> btw, is it normal that a compile eats up this much space?
> Is there any way to avoid it when writing new code?
g++-3.4 is definitely better in memory usage, although to test this
you would have to recompile all C++ dependent build dependencies
first.
