public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: felix-gcc@fefe.de, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org
Subject: Re: c++/8889: g++ 3.2.1 (also 3.2 it) miscompile Qt
Date: Mon, 16 Dec 2002 11:26:00 -0000	[thread overview]
Message-ID: <20021216192625.14427.qmail@sources.redhat.com> (raw)

Synopsis: g++ 3.2.1 (also 3.2 it) miscompile Qt

State-Changed-From-To: open->feedback
State-Changed-By: bangerth
State-Changed-When: Mon Dec 16 11:26:23 2002
State-Changed-Why:
    I'm still leaning with Volker's ABI theory. What one
    would need to check is what libraries Qt actually pulls
    in. For example, on my system these are:
    tmp/g> ldd /usr/lib/libqt.so.3
            libpng.so.2 => /usr/lib/libpng.so.2 (0x40618000)
            libz.so.1 => /lib/libz.so.1 (0x40649000)
            libGL.so.1 => /usr/lib/libGL.so.1 (0x40658000)
            libXmu.so.6 => /usr/X11R6/lib/libXmu.so.6 (0x4080f000)
            libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x40826000)
            libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x4083e000)
            libdl.so.2 => /lib/libdl.so.2 (0x40848000)
            libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x4084c000)
            libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x4085a000)
            libXrender.so.1 => /usr/X11R6/lib/libXrender.so.1 (0x4091a000)
            libXft.so.1 => /usr/X11R6/lib/libXft.so.1 (0x40920000)
            libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x4094a000)
            libstdc++-libc6.2-2.so.3 => /usr/lib/libstdc++-libc6.2-2.so.3 (0x4098a000)
            libm.so.6 => /lib/libm.so.6 (0x409d7000)
            libc.so.6 => /lib/libc.so.6 (0x409fa000)
            libXt.so.6 => /usr/X11R6/lib/libXt.so.6 (0x40b22000)
            libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0x40b70000)
            /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
    
    
    On my system, these libraries all contain no C++ symbols,
    except libstdc++, of course, but you should repeat this
    with the executables/libraries that fail for you.
    
    Please understand that we do not want to push away
    responsibility for possible bugs to you, but that simple
    the problem you describe is so vague, and the piece of
    code in which it happens so large, that there is about
    no way for us to track this problem down. So we just
    try to eliminate the simple problems first.
    
    Regards
      Wolfgang

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8889


             reply	other threads:[~2002-12-16 19:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-16 11:26 bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-16 17:26 Zack Weinberg
2002-12-16 17:06 Felix von Leitner
2002-12-16 16:08 bangerth
2002-12-16 16:06 Wolfgang Bangerth
2002-12-16 16:06 Wolfgang Bangerth
2002-12-16 15:26 Wolfgang Bangerth
2002-12-16 13:06 Wolfgang Bangerth
2002-12-16 12:56 Felix von Leitner
2002-12-12  8:12 reichelt
2002-12-12  7:06 Felix von Leitner
2002-12-12  2:50 reichelt

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=20021216192625.14427.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=felix-gcc@fefe.de \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).