Your message dated Sat, 9 Oct 2004 08:39:31 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#248366: g++-3.3 ICE's due to missing /proc 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; 10 May 2004 19:37:22 +0000 >From [EMAIL PROTECTED] Mon May 10 12:37:22 2004 Return-path: <[EMAIL PROTECTED]> Received: from 233pc233.sshunet.nl (mordor.wolffelaar.nl) [131.211.233.233] (mail) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1BNGaY-0007dR-00; Mon, 10 May 2004 12:37:22 -0700 Received: from jeroen by mordor.wolffelaar.nl with local (Exim 3.36 #1 (Debian)) id 1BNGaV-0007Mt-00 for <[EMAIL PROTECTED]>; Mon, 10 May 2004 21:37:19 +0200 Date: Mon, 10 May 2004 21:37:19 +0200 From: Jeroen van Wolffelaar <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: g++-3.3 1:3.3.3-7 starts to give ICE's on both i386 and powerpc Message-ID: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Reportbug-Version: 2.58 User-Agent: Mutt/1.5.5.1+cvs20040105i 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=-7.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: X-CrossAssassin-Score: 1 Package: g++-3.3 Version: 1:3.3.3-7 Severity: serious Justification: Causes other packages to FTBFS With 1:3.3.3-6 (no bug) or -7 (bug): # apt-get build-dep povray-3.5 $ apt-get source povray-3.5 $ cd povray-3.5-3.5.0c/src $ i386-linux-g++ -DPREFIX=\"/usr\" \ -DPOV_LIB_DIR=\"/usr/share/povray-3.5\" \ -DCOMPILER_VER=\".Linux.i386-linux-gcc\" \ -DSYSCONFDIR=\"/etc/povray-3.5\" -DUSE_IO_RESTRICTIONS=\"\" -I. \ -I. -I. -W -O3 -finline-functions -ffast-math \ -fomit-frame-pointer -fexpensive-optimizations \ -foptimize-sibling-calls -minline-all-stringops -funroll-loops \ -Wno-multichar -MT bezier.o -MD -MP -MF ".deps/bezier.Tpo" -c -o \ bezier.o bezier.cpp If -6, if succeeds, if -7, it fails with this output: | bezier.cpp: In function `void bezier_bounding_sphere(double | (*)[4][4][3], | double*, double*)': | bezier.cpp:859: internal compiler error: Segmentation fault | Please submit a full bug report, | with preprocessed source if appropriate. | See <URL:http://gcc.gnu.org/bugs.html> for instructions. Note that I couldn't get -save-temps to trigger the same error. --Jeroen -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.3 Locale: LANG=C, LC_CTYPE=C (ignored: LC_ALL set to C) ### IMPORTANT: this info is from my Sarge system, it's definitely only ### g++ causing the problems (-7) Versions of packages g++-3.3 depends on: ii gcc-3.3 1:3.3.3-6 The GNU C compiler ii gcc-3.3-base 1:3.3.3-6 The GNU Compiler Collection (base ii libc6 2.3.2.ds1-12 GNU C Library: Shared libraries an ii libstdc++5-3.3-dev 1:3.3.3-6 The GNU Standard C++ Library v3 (d -- no debconf information -- Jeroen van Wolffelaar [EMAIL PROTECTED] http://jeroen.A-Eskwadraat.nl --------------------------------------- Received: (at 248366-done) by bugs.debian.org; 9 Oct 2004 06:39:35 +0000 >From [EMAIL PROTECTED] Fri Oct 08 23:39:35 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 1CGAtD-000651-00; Fri, 08 Oct 2004 23:39:35 -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 IAA20215; Sat, 9 Oct 2004 08:39:33 +0200 (MEST) Received: from localhost (localhost [127.0.0.1]) by mailhost.cs.tu-berlin.de (Postfix) with ESMTP id BA35DF219; Sat, 9 Oct 2004 08:39:32 +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 16364-03; Sat, 9 Oct 2004 08:39:32 +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; Sat, 9 Oct 2004 08:39:32 +0200 (MEST) Received: (from [EMAIL PROTECTED]) by bolero.cs.tu-berlin.de (8.12.10+Sun/8.12.8/Submit) id i996dWCH013728; Sat, 9 Oct 2004 08:39:32 +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: Sat, 9 Oct 2004 08:39:31 +0200 To: Jeroen van Wolffelaar <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Subject: Re: Bug#248366: g++-3.3 ICE's due to missing /proc 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=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Jeroen van Wolffelaar writes: > On Tue, Jun 29, 2004 at 02:20:07AM +0900, GOTO Masanori wrote: > > At Mon, 28 Jun 2004 10:39:08 +0200, > > Jeroen van Wolffelaar wrote: > > > On Mon, Jun 28, 2004 at 10:18:08AM +0900, GOTO Masanori wrote: > > > > At Sun, 27 Jun 2004 09:24:36 +0200, > > > > Matthias Klose wrote: > > > > > The bug submitter claims that a missing /proc leads to ICE's in gcc > > > > > and thinks this might be a bug in glibc or gcc. Any ideas? I'm unable > > > > > to reproduce this one. > > > > > > > > strace give us some more hints. > > > > BTW, why did Jeroen use 2.6.3? AFAIK some early 2.6.* has problems. > > > > > > I simply didn't upgrade yet. I'll do that soon then. By the way, are you > > > asking me to do a strace, or do you mean that you did so, and already > > > have a hint of what the problem might me? > > > > Please do a strace. I can't reproduce your bug with normal gcc > > compilation. > > With kernel 2.6.7 and sid's gcc etc I cannot reproduce this anymore > either. > > Maybe it was the kernel, maybe something else. I guess it's quite > untrackable anymore, and also not so relevant since I cannot reproduce > it on current sid. I suggest closing this bug, but if you want to maybe > do something with it, you can keep it open... > > Thanks for trying to reproduce this! closing the report.