From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21665 invoked by alias); 2 Dec 2004 22:33:12 -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 21523 invoked from network); 2 Dec 2004 22:33:03 -0000 Received: from unknown (HELO mail1.thewrittenword.com) (67.95.107.114) by sourceware.org with SMTP; 2 Dec 2004 22:33:03 -0000 Received: by mail1.thewrittenword.com (Postfix, from userid 1000) id 0252E215; Thu, 2 Dec 2004 16:33:02 -0600 (CST) Date: Thu, 02 Dec 2004 22:33:00 -0000 From: Albert Chin To: gcc@gcc.gnu.org Subject: SEGV building qt-3.3.3 with GCC 3.4.3 on RH 7.1/RHEL 2.1 Message-ID: <20041202223302.GA90088@mail1.thewrittenword.com> Reply-To: gcc@gcc.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i X-SW-Source: 2004-12/txt/msg00156.txt.bz2 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: ... /opt/build/qt-x11-free-3.3.2/bin/uic -L /opt/build/qt-x11-free-3.3.2/plugins projectsettings.ui -i projectsettings.h -o projectsettings.cpp gmake[4]: *** [projectsettings.cpp] Segmentation fault (core dumped) Trying to debug it (with gdb-6.3): $ cd /opt/build/qt-x11-free-3.3.3/tools/designer/plugins/cppeditor $ gdb /opt/build/qt-x11-free-3.3.2/bin/uic core gdb> bt #0 0x40e6c36c in ?? () #1 0x40ce456b in exit (status=0) at exit.c:54 #2 0x40ccf690 in __libc_start_main (main=0x8051550
, argc=8, ubp_av=0xbffed604, init=0x80501bc <_init>, fini=0x808bfa0 <_fini>, rtld_fini=0x4000dda4 <_dl_fini>, stack_end=0xbffed5fc) at ../sysdeps/generic/libc-start.c:129 #3 0x08051361 in _start () I tried adding print statements to main() but it didn't help. The last statement in main() is 'return 0;' and everything works ok up until this point. The SEGV appears _after_ the return statement. $ gcc -v Reading specs from /opt/TWWfsw/gcc343/lib/gcc/i686-redhat-linuxe2.1/3.4.3/specs Configured with: /opt/build/gcc-3.4.3/configure --with-included-gettext --enable-libgcj --enable-__cxa_atexit --with-gnu-as --with-as=/opt/TWWfsw/gcc343/i686-redhat-linuxe2.1/bin/as --with-gnu-ld --with-ld=/opt/TWWfsw/gcc343/i686-redhat-linuxe2.1/bin/ld --datadir=/opt/TWWfsw/gcc343/share --host=i686-redhat-linuxe2.1 --with-local-prefix=/opt/TWWfsw/gcc343 --prefix=/opt/TWWfsw/gcc343 Thread model: posix gcc version 3.4.3 (TWW) Both 3.4.2 and 3.4.3 are built against binutils-2.15 as/ld. According to http://gcc.gnu.org/install/specific.html#*-*-linux*: Versions of libstdc++-v3 starting with 3.2.1 require bugfixes present in glibc 2.2.5 and later. More information is available in the libstdc++-v3 documentation. >From the libstdc++-v3 documentation, this requirement is for a locale issue so I don't think it's the cause for the above problem. 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? -- albert chin (china@thewrittenword.com)