[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#238552: marked as done (gcc: Internal error: Killed)



Your message dated Wed, 17 Mar 2004 22:30:30 +0100
with message-id <87u10nrwjt.fsf@informatik.uni-tuebingen.de>
and subject line Bug#238552: gcc "crash"
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; 17 Mar 2004 16:33:51 +0000
>From jdorje@users.sourceforge.net Wed Mar 17 08:33:51 2004
Return-path: <jdorje@users.sourceforge.net>
Received: from cpe-024-211-229-193.ec.rr.com (devon.dhs.org) [24.211.229.193] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1B3dzL-0004Ax-00; Wed, 17 Mar 2004 08:33:51 -0800
Received: from jdorje by devon.dhs.org with local (Exim 3.36 #1 (Debian))
	id 1B3dwG-00056h-00; Wed, 17 Mar 2004 11:30:40 -0500
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Jason Dorje Short <jdorje@users.sourceforge.net>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: gcc: Internal error: Killed
X-Mailer: reportbug 2.53
Date: Wed, 17 Mar 2004 11:30:39 -0500
Message-Id: <[🔎] E1B3dwG-00056h-00@devon.dhs.org>
Sender: Jason Dorje Short <jdorje@debian>
X-BadReturnPath: jdorje@debian rewritten as jdorje@users.sourceforge.net
  using "From" header
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_12 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-7.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
	autolearn=no version=2.60-bugs.debian.org_2004_03_12
X-Spam-Level: 

Package: gcc-3.3
Version: 1:3.3.3-3
Severity: normal

I was compiling some source when gcc exited.  The message it gave was:

gcc: Internal error: Killed (program cc1)
Please submit a full bug report.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
For Debian GNU/Linux specific bugs,
please see /usr/share/doc/debian/bug-reporting.txt.

So here I am, reporting the bug.  However this bug report doesn't seem 
helpful becase the problem is not reproducable.  When I compile again it 
works fine.

I can give some information, though.  I was compiling several copies of 
the code simultaneously.  That is, I had one source tree (src/freeciv) 
and several build trees (src/gtk, src/xaw, etc.) running builds 
simultaneously.  In fact these trees were probably building the same 
file all at once (since one of the files takes much longer to compile 
than the others).  Also, I use ccache.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.24-1-686
Locale: LANG=C, LC_CTYPE=C

Versions of packages gcc-3.3 depends on:
ii  binutils                   2.14.90.0.7-5 The GNU assembler, linker and bina
ii  cpp-3.3                    1:3.3.3-3     The GNU C preprocessor
ii  gcc-3.3-base               1:3.3.3-3     The GNU Compiler Collection (base 
ii  libc6                      2.3.2.ds1-11  GNU C Library: Shared libraries an
ii  libgcc1                    1:3.3.3-3     GCC support library

-- no debconf information

---------------------------------------
Received: (at 238552-done) by bugs.debian.org; 17 Mar 2004 21:31:05 +0000
>From hueffner@informatik.uni-tuebingen.de Wed Mar 17 13:31:05 2004
Return-path: <hueffner@informatik.uni-tuebingen.de>
Received: from mx5.informatik.uni-tuebingen.de [134.2.12.32] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1B3icy-0002H0-00; Wed, 17 Mar 2004 13:31:04 -0800
Received: from localhost (loopback [127.0.0.1])
	by mx5.informatik.uni-tuebingen.de (Postfix) with ESMTP id F0BE4128
	for <238552-done@bugs.debian.org>; Wed, 17 Mar 2004 22:30:32 +0100 (NFT)
Received: from mx3.informatik.uni-tuebingen.de ([134.2.12.26])
 by localhost (mx5 [134.2.12.32]) (amavisd-new, port 10024) with ESMTP
 id 44604-03 for <238552-done@bugs.debian.org>;
 Wed, 17 Mar 2004 22:30:31 +0100 (NFT)
Received: from juist (semeai [134.2.15.66])
	by mx3.informatik.uni-tuebingen.de (Postfix) with ESMTP id 93758134
	for <238552-done@bugs.debian.org>; Wed, 17 Mar 2004 22:30:30 +0100 (NFT)
Received: from falk by juist with local (Exim 3.36 #1 (Debian))
	id 1B3icQ-00025Q-00
	for <238552-done@bugs.debian.org>; Wed, 17 Mar 2004 22:30:30 +0100
To: 238552-done@bugs.debian.org
Subject: Re: Bug#238552: gcc "crash"
References: <[🔎] 4058833D.6020402@users.sf.net>
	<[🔎] 87n06fgyx2.fsf@informatik.uni-tuebingen.de>
	<[🔎] 4058B0EA.4050309@users.sf.net>
From: Falk Hueffner <hueffner@informatik.uni-tuebingen.de>
X-Face: "iUeUu$b*W_"w?tV83Y3*r:`rh&dRv}$YnZ3,LVeCZSYVuf[Gpo*5%_=/\_!gc_,SS}[~xZ
 wY77I-M)xHIx:2f56g%/`SOw"Dx%4Xq0&f\Tj~>|QR|vGlU}TBYhiG(K:2<T^
Date: Wed, 17 Mar 2004 22:30:30 +0100
In-Reply-To: <[🔎] 4058B0EA.4050309@users.sf.net> (Jason Dorje Short's message of
 "Wed, 17 Mar 2004 15:11:22 -0500")
Message-ID: <87u10nrwjt.fsf@informatik.uni-tuebingen.de>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.5 (cabbage, linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Virus-Scanned: by amavisd-new (McAfee AntiVirus) at informatik.uni-tuebingen.de
Delivered-To: 238552-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_12 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-5.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
	autolearn=no version=2.60-bugs.debian.org_2004_03_12
X-Spam-Level: 

Jason Dorje Short <jdorje@users.sourceforge.net> writes:

> Falk Hueffner wrote:
>> Nearly certainly you're running out of memory. Please check that with
>> top.
>
> Indeed, that seems to be the case.  Somehow my swap has been turned
> off.
>
> My only suggestion is that gcc could probably give a better error
> message.

That'd be difficult. gcc just gets a SIGKILL and canot know it was
because of out of memory, or maybe the user just sent it.

Therefore I close this bug.

-- 
	Falk



Reply to: