public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sega01 at go-beyond dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/39852]  New: GCC 4.4.0 builds a broken glibc 2.8
Date: Wed, 22 Apr 2009 15:31:00 -0000	[thread overview]
Message-ID: <bug-39852-17612@http.gcc.gnu.org/bugzilla/> (raw)

Hi,

Sorry for the lack of testing and specificity, but this should be fairly easy
to reproduce. Another user on Freenode's #gcc reported the same problem, so I
don't think it's just my setup. #gcc suggested I use a static gdb for
debugging, but for now I will link to some ltrace and strace dumps.

GCC 4.3.3 (about the latest snapshot, or any version) builds glibc 2.8
(snapshot) just fine, and it seems to be perfectly stable. A few days ago I
wanted to give 4.4.0 a try, so I built GCC, and rebuilt gcc and binutils from
the new GCC. Everything seemed to go fine, so I went on to glibc. glibc built
fine, but after upgrading to it I noticed that most glibc-linked (which is just
about everything on my box) applications segfaulted. Fortunately, strace and
ltrace were seemingly unaffected.

Common patterns I noticed with what broke and what didn't were that Coreutils
stuff broke along with GCC, Bash, nano, sed, vi, but module-init-tools,
Busybox, nsudoku, Pacman, osstest, and time all run just fine (as in no
segfaults).

http://pastebin.com/f21432957 has ltraces and straces of several binaries
linked to glibc that segfault. Let me know if I should do l/straces of binaries
that don't segfault or try something else. This should be quite reproducible
though. Should I try anything else? Sorry for my lack of informedness in this
area, I'll try to learn more when I have the time. This is on Icadyptes, my
Arch Linux fork. I build just about everything with -march=i486 -mtune=generic
-O2 -fomit-frame-pointer -pipe, if it helps. This is on Linux 2.6.28/2.6.29.

[root@silentgnu ~]# gcc -v
Using built-in specs.
Target: i486-pc-linux-gnu
Configured with: ../configure --prefix=/usr --enable-shared
--enable-languages=c,c++ --enable-threads=posix --enable-__cxa_atexit
--disable-multilib --libdir=/usr/lib --libexecdir=/usr/lib --enable-clocale=gnu
--disable-libstdcxx-pch --with-tune=generic --host=i486-pc-linux-gnu
--target=i486-pc-linux-gnu --build=i486-pc-linux-gnu
Thread model: posix
gcc version 4.4.0 (GCC)

Thanks,
Teran

PS: Great job on GCC, I was impressed to find that GCC 4.4.0 generally built
smaller binaries than 4.3.3. I didn't get to do any benchmarking, but keep up
the good work :-).


-- 
           Summary: GCC 4.4.0 builds a broken glibc 2.8
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Severity: major
          Priority: P3
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: sega01 at go-beyond dot org
 GCC build triplet: i486-pc-linux-gnu
  GCC host triplet: i486-pc-linux-gnu
GCC target triplet: i486-pc-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39852


             reply	other threads:[~2009-04-22 15:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-22 15:31 sega01 at go-beyond dot org [this message]
2009-04-23  0:09 ` [Bug middle-end/39852] " pinskia at gcc dot gnu dot org
2009-04-23  0:55 ` sega01 at go-beyond dot org
2009-04-23  0:57 ` pinskia at gcc dot gnu dot org
2009-04-23  1:10 ` sega01 at go-beyond dot org
2009-04-23  6:04 ` jakub at gcc dot gnu dot org
2009-04-23 20:59 ` sega01 at go-beyond dot org
2010-02-01  8:50 ` thunderwolf66102 at yahoo dot com
2010-02-01 11:14 ` mikpe at it dot uu dot se

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=bug-39852-17612@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).