Signal 11/Signal 10 Instability?

Hi, i've recently switched to -CURRENT after being a long time Linux
user.  That probably isn't working in my favor.

Today's most recently supped and builded current (as well as for the past
few days) has yielded some interesting problems:

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.

I do in fact have a libmap.conf:

libc_r.so.5     libpthread.so.1
libc_r.so       libpthread.so

Which I understand is the general cause of this type of behavior.

I'm curious as to what I need to be doing to debug this problem and determine
whether it is something in -CURRENT.

Feel free to respond privately if this isn't appropriate for the current ml.

Thanks,
Tim