From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22079 invoked by alias); 3 Dec 2004 17:13:51 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 22053 invoked from network); 3 Dec 2004 17:13:47 -0000 Received: from unknown (HELO mail1.thewrittenword.com) (67.95.107.114) by sourceware.org with SMTP; 3 Dec 2004 17:13:47 -0000 Received: by mail1.thewrittenword.com (Postfix, from userid 1000) id AC18A1E4; Fri, 3 Dec 2004 11:13:47 -0600 (CST) Date: Fri, 03 Dec 2004 17:13:00 -0000 From: Albert Chin To: gcc@gcc.gnu.org Subject: Re: SEGV building qt-3.3.3 with GCC 3.4.3 on RH 7.1/RHEL 2.1 Message-ID: <20041203171347.GA32781@mail1.thewrittenword.com> Reply-To: gcc@gcc.gnu.org References: <20041202223302.GA90088@mail1.thewrittenword.com> <20041202160806.A1814@synopsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041202160806.A1814@synopsys.com> User-Agent: Mutt/1.5.6i X-SW-Source: 2004-12/txt/msg00181.txt.bz2 On Thu, Dec 02, 2004 at 04:08:06PM -0800, Joe Buck wrote: > On Thu, Dec 02, 2004 at 04:33:02PM -0600, Albert Chin wrote: > > Just build Qt-3.3.3 with GCC 3.4.2 and 3.4.3 on Redhat Linux 7.1/x86 > > and RHEL 2.1/x86. No problems with 3.4.2. However, when building with > > 3.4.3, I get a segfault during the build: > > ... > > Redhat Linux 9/x86, RHEL 3.0/x86, and RHEL 3.0/amd64 work fine. I > > reviewed http://gcc.gnu.org/gcc-3.4/changes.html#3.4.3 but nothing > > stands out as to what causes this. Where should I start looking? > > Are you saying that you get a segfault when you build with 3.4.3 on RHEL > 2.1, but not when you build with 3.4.3 on RHEL 3.0 or RH9? If so, this > doesn't sound like the compiler is at fault. A KDE developers' list might > be a better place to track this one down, but I don't see any alternative > to just debugging the problem. If the blowup is in a place where there > appears to be no code, it's probably in a destructor. Sorry, my fault. I incorrectly installed binutils-2.15 so gcc-3.4.3 never built against it. -- albert chin (china@thewrittenword.com)