This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: c++/8889: g++ 3.2.1 (also 3.2 it) miscompile Qt
- From: bangerth at dealii dot org
- To: felix-gcc at fefe dot de, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org
- Date: 16 Dec 2002 19:26:25 -0000
- Subject: Re: c++/8889: g++ 3.2.1 (also 3.2 it) miscompile Qt
- Reply-to: bangerth at dealii dot org, felix-gcc at fefe dot de, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, gcc-gnats at gcc dot gnu dot org
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