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 middle-end/39852] GCC 4.4.0 builds a broken glibc 2.8
Date: Thu, 23 Apr 2009 01:10:00 -0000	[thread overview]
Message-ID: <20090423011007.10243.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39852-17612@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from sega01 at go-beyond dot org  2009-04-23 01:10 -------
(In reply to comment #3)
> It might be better if you use gdb instead of using ltrace because those two
> programs don't give enough information on what is going on.  This could be
> still a bug in Lua or even in glibc itself but without a testcase to figure out
> what is going wrong it is hard to debug.
> 

I can give gdb a try, but will let this sit for tonight first. For clarity,
nothing on my system is compiled with GCC 4.4.0 except glibc 2.8 for when I
test. Lua, xz, vi, nano, and all of the programs that segfault only segfault
when I use the GCC 4.4.0 compiled glibc 2.8; if I use glibc 2.8 built with GCC
4.3.3 they run just fine. I don't think this is a bug in any of those programs.
I think this could be a glibc bug, but I'm leaning on GCC since GCC 4.3.3
builds a clean glibc.

Thanks,
Teran


-- 


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


  parent reply	other threads:[~2009-04-23  1:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-22 15:31 [Bug c/39852] New: " sega01 at go-beyond dot org
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 [this message]
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
     [not found] <bug-39852-4@http.gcc.gnu.org/bugzilla/>
2011-12-21 23:48 ` pinskia at gcc dot gnu.org

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=20090423011007.10243.qmail@sourceware.org \
    --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).