Re: Signal 11/Signal 10 Instability?

On Sun, Aug 08, 2004 at 07:16:36PM -0400, Tim wrote:
> pid 31350 (glxinfo), uid 1001: exited on signal 11 (core dumped)
> pid 32991 (uic), uid 0: exited on signal 11 (core dumped)
> pid 34460 (uic), uid 0: exited on signal 11 (core dumped)
> pid 34480 (firefox-bin), uid 1001: exited on signal 10 (core dumped)
> pid 38612 (firefox-bin), uid 1001: exited on signal 10
> pid 38653 (firefox-bin), uid 1001: exited on signal 10
> pid 38673 (glxgears), uid 1001: exited on signal 11
> pid 38707 (firefox-bin), uid 1001: exited on signal 10
> pid 38744 (firefox-bin), uid 1001: exited on signal 10 (core dumped)
> pid 66084 (uic), uid 0: exited on signal 11 (core dumped)
> pid 66170 (uic), uid 0: exited on signal 11 (core dumped)
> pid 66255 (uic), uid 0: exited on signal 11 (core dumped)
> 
> Those are from dmesg.  The last three most recent ones are from attempts
> to build djvulibre, which depends on Qt.   The system hasn't crashed or
> anything, but i'm wondering if i'm missing something.

This could have been caused by the recent gcc 3.4.2 upgrade.
gcc broke ABI compat once again, and you need to recompile
every C++ app. See /usr/src/UPDATING:

20040728:
        System compiler has been upgraded to GCC 3.4.2-pre. As with any major
        compiler upgrade, there are several issues to be aware of. GCC 3.4.x
        has broken C++ ABI compatibility with previous releases yet again
        and users will have to rebuild all their C++ programs with the new
        compiler. A new unit-at-a-time optimization mode, which is default
        in this compiler release, is more aggressive in removing unused
        static symbols. This is the likely cause of 'make buildworld'
        breakages with non-default CFLAGS where optimization level is set
        to -O2 or higher.

G'luck!

-cpghost.

-- 
Cordula's Web. http://www.cordula.ws/