public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Albert Chin <gcc@mlists.thewrittenword.com>
To: gcc@gcc.gnu.org
Subject: SEGV building qt-3.3.3 with GCC 3.4.3 on RH 7.1/RHEL 2.1
Date: Thu, 02 Dec 2004 22:33:00 -0000	[thread overview]
Message-ID: <20041202223302.GA90088@mail1.thewrittenword.com> (raw)

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 <main>, 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)

             reply	other threads:[~2004-12-02 22:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-02 22:33 Albert Chin [this message]
2004-12-03  0:08 ` Joe Buck
2004-12-03 17:13   ` Albert Chin
2004-12-07 15:56   ` Nix
2004-12-09 20:46   ` Michael Matz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041202223302.GA90088@mail1.thewrittenword.com \
    --to=gcc@mlists.thewrittenword.com \
    --cc=gcc@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).