Date: Thu, 15 Nov 2007 09:24:32 -0600 From: David J Brooks <freysman@comcast.net> To: freebsd-questions@freebsd.org Cc: "Heiko Wundram \(Beenic\)" <wundram@beenic.net> Subject: Re: python25 core dumps Message-ID: <200711150924.34152.freysman@comcast.net> In-Reply-To: <200711151007.03334.wundram@beenic.net> References: <200711141615.37380.freysman@comcast.net> <200711142107.27718.freysman@comcast.net> <200711151007.03334.wundram@beenic.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 15 November 2007 03:07:03 am Heiko Wundram (Beenic) wrote: > This seems like a problem in libaspell; maybe you should simply try to > reinstall the aspell port. See below for more info. I rebuilt aspell, but gramps still core dumps. The backtrace shows the same as previously. :/ > > For comparison, this is what a crash from eric4 (built with PyQt4) looks > > like: <snip backtrace> > This seems like a problem in qt4 (I don't think the problem is in PyQt), > simply try reinstalling that, too (completely; qt4 is split into several > ports and "pkg_info | grep qt4" is your friend here). > > Generally, from what I interpret into the second backtrace, you upgraded > from some 6 release to 7.0-BETA2, which (amongst other things) means that > the C++ libraries have changed (because of a newer compiler, gcc 3.3 vs. > 4.2). The compiler has also had changes introduced to the C++ type info > descriptor layout (which I should think causes the segmentation fault in > typeinfo name in the second backtrace), so that if you have a program > that's linked against different versions of libstdc++ (PyQt is linked > against that, just as qt4 is), you'll see behaviour like this. > > To check whether my hypothesis is correct, simply do an ldd on both a PyQt > library, and a qt4 shared library (locations of both of which you can > extract from the backtrace). If the version of libstdc++ is different, you > didn't follow the upgrading procedure which explicitly states to recompile > _all_ ports for the new system. These appear to be the same, but its possible my blurry eyes may be overlooking something obvious. /usr/local/lib/libQtGui.so.4: libpng.so.5 => /usr/local/lib/libpng.so.5 (0x28185000) libSM.so.6 => /usr/local/lib/libSM.so.6 (0x281aa000) libICE.so.6 => /usr/local/lib/libICE.so.6 (0x281b2000) libQtCore.so.4 => /usr/local/lib/libQtCore.so.4 (0x28a1a000) libz.so.4 => /lib/libz.so.4 (0x281c9000) libgthread-2.0.so.0 => /usr/local/lib/libgthread-2.0.so.0 (0x281db000) libglib-2.0.so.0 => /usr/local/lib/libglib-2.0.so.0 (0x28b89000) libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x28c27000) libXi.so.6 => /usr/local/lib/libXi.so.6 (0x281e0000) libXrender.so.1 => /usr/local/lib/libXrender.so.1 (0x281e8000) libXrandr.so.2 => /usr/local/lib/libXrandr.so.2 (0x281f0000) libXfixes.so.3 => /usr/local/lib/libXfixes.so.3 (0x281f7000) libXcursor.so.1 => /usr/local/lib/libXcursor.so.1 (0x28d1c000) libXinerama.so.1 => /usr/local/lib/libXinerama.so.1 (0x281fc000) libfreetype.so.9 => /usr/local/lib/libfreetype.so.9 (0x28d25000) libfontconfig.so.1 => /usr/local/lib/libfontconfig.so.1 (0x28d93000) libXext.so.6 => /usr/local/lib/libXext.so.6 (0x28dbd000) libX11.so.6 => /usr/local/lib/libX11.so.6 (0x28dcb000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x28eb8000) libm.so.5 => /lib/libm.so.5 (0x28fa2000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x28fb7000) libthr.so.3 => /lib/libthr.so.3 (0x28fc2000) libc.so.7 => /lib/libc.so.7 (0x28089000) libintl.so.8 => /usr/local/lib/libintl.so.8 (0x28fd4000) libpcre.so.0 => /usr/local/lib/libpcre.so.0 (0x28fdd000) libexpat.so.6 => /usr/local/lib/libexpat.so.6 (0x29003000) libXau.so.6 => /usr/local/lib/libXau.so.6 (0x29023000) libXdmcp.so.6 => /usr/local/lib/libXdmcp.so.6 (0x29026000) librpcsvc.so.4 => /usr/lib/librpcsvc.so.4 (0x2902b000) /usr/local/lib/python2.5/site-packages/PyQt4/QtGui.so: libQtGui.so.4 => /usr/local/lib/libQtGui.so.4 (0x28b09000) libpng.so.5 => /usr/local/lib/libpng.so.5 (0x28185000) libSM.so.6 => /usr/local/lib/libSM.so.6 (0x281aa000) libICE.so.6 => /usr/local/lib/libICE.so.6 (0x281b2000) libQtCore.so.4 => /usr/local/lib/libQtCore.so.4 (0x29223000) libz.so.4 => /lib/libz.so.4 (0x281c9000) libgthread-2.0.so.0 => /usr/local/lib/libgthread-2.0.so.0 (0x281db000) libglib-2.0.so.0 => /usr/local/lib/libglib-2.0.so.0 (0x29392000) libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x29430000) libXi.so.6 => /usr/local/lib/libXi.so.6 (0x281e0000) libXrender.so.1 => /usr/local/lib/libXrender.so.1 (0x281e8000) libXrandr.so.2 => /usr/local/lib/libXrandr.so.2 (0x281f0000) libXfixes.so.3 => /usr/local/lib/libXfixes.so.3 (0x281f7000) libXcursor.so.1 => /usr/local/lib/libXcursor.so.1 (0x29525000) libXinerama.so.1 => /usr/local/lib/libXinerama.so.1 (0x281fc000) libfreetype.so.9 => /usr/local/lib/libfreetype.so.9 (0x2952e000) libfontconfig.so.1 => /usr/local/lib/libfontconfig.so.1 (0x2959c000) libXext.so.6 => /usr/local/lib/libXext.so.6 (0x295c6000) libX11.so.6 => /usr/local/lib/libX11.so.6 (0x295d4000) libm.so.5 => /lib/libm.so.5 (0x296c1000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x296d6000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x297c0000) libthr.so.3 => /lib/libthr.so.3 (0x297cb000) libc.so.7 => /lib/libc.so.7 (0x28089000) libintl.so.8 => /usr/local/lib/libintl.so.8 (0x297dd000) libpcre.so.0 => /usr/local/lib/libpcre.so.0 (0x297e6000) libexpat.so.6 => /usr/local/lib/libexpat.so.6 (0x2980c000) libXau.so.6 => /usr/local/lib/libXau.so.6 (0x2982c000) libXdmcp.so.6 => /usr/local/lib/libXdmcp.so.6 (0x2982f000) librpcsvc.so.4 => /usr/lib/librpcsvc.so.4 (0x29834000) > There are also some other changes, especially in the threading libraries, > which can cause errors like these on non-C++ applications, although I > wouldn't know whether aspell is affected by this, but possibly gtk2 is. > > Anyway, posting some more info on the upgrade process to 7.0 you did would > help, I guess. I initially tried to upgrade all ports using 'portupgrade -fa', which ran for days and left me with 11 ports failed and about 300 skipped as a result. I managed to upgrade the failed ones with 'make install' then 'portupgrade -fa' again, rather than trying to upgrade the skipped 300 one at a time. When this ran into the same series of failures as before I realized the error and simply removed all ports 'pkg_delete -f \*' and reinstalled them using 'pkg_add -r'. I am currently in the process of 'portupgrade -aR' following a recent portsnap which shows a small handful of packages needing upgrades. David -- This message is LOADING...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200711150924.34152.freysman>