Guys, I have stumbled onto a strange issue with glibc 2.13-4 issue on Arch Linux that only effects the Trinity desktop build on x86_64 boxes. I have confirmed this behavior on 3 different x86_64 boxes. i686 does not exhibit this behavior and downgrading to 2.13-3 fixes it. I have built glibc and libxcb with CFLAGS="$CFLAGS -g" and the basic crash error I get is:
#5 0x00007fc401274655 in raise () from /lib/libc.so.6 #6 0x00007fc401275ad6 in abort () from /lib/libc.so.6 #7 0x00007fc4012ae7eb in ?? () from /lib/libc.so.6 #8 0x00007fc4012b3b96 in ?? () from /lib/libc.so.6 #9 0x00007fc4012b64ad in ?? () from /lib/libc.so.6 #10 0x00007fc4012b8460 in malloc () from /lib/libc.so.6 #11 0x00007fc3fd7fa91a in _xcb_in_read () from /usr/lib/libxcb.so.1 #12 0x00007fc3fd7f8bfa in _xcb_conn_wait () from /usr/lib/libxcb.so.1 #13 0x00007fc3fd7fa1af in xcb_wait_for_reply () from /usr/lib/libxcb.so.1 #14 0x00007fc401b07afd in _XReply () from /usr/lib/libX11.so.6 #15 0x00007fc401af1714 in XInternAtom () from /usr/lib/libX11.so.6 Full kcrash file here: http://www.3111skyline.com/dl/dt/trinity/arch/err/x86_64/kdesktop-libxcb+glibc-debug.kcrash I isolated this to glibc 2.13-4 when I started an older Arch install that still had 2.13-3 on it and there was no kdesktop crash. I then updated that Arch install to 2.13-4 and got the crash on reboot/restart of the box and Trinity. The relevant files updated on the box were: [2011-02-22 11:13] upgraded glibc (2.13-3 -> 2.13-4) <snip> [2011-02-22 11:17] upgraded kernel26 (2.6.37-6 -> 2.6.37.1-1) [2011-02-22 11:17] upgraded kernel26-headers (2.6.37-6 -> 2.6.37.1-1) <snip> [2011-02-22 11:18] upgraded trinity-kdelibs (1220926-1 -> 1222098-1) [2011-02-22 11:18] upgraded trinity-kdebase (1221507-1 -> 1221588-1) I hadn't rebuilt glibc with debug on this box, so the kcrash info is a bit more sparse: http://www.3111skyline.com/dl/dt/trinity/arch/err/x86_64/kdesktop-alchemy.kcrash So then I downgraded glibc (2.13-4 -> 2.13-3), restarted Trinity -> perfect! No kdesktop,kcrash at all and everything was working as it should. From my first gcc bug reported, http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47723, I learned it wasn't gcc at all, but an intentional change in gcc >= 4.5 that required the class constructors in Trinity to be updated. Before filing, I wanted to check here to see: (1) if this is the right place for the glibc issue; and (2) if you think it is something that should be filed or whether the error points to a packaging problem or a problem with the Trinity source. With my limited glibc bug identifying knowledge, "if updating glibc breaks it, downgrading glibc fixes it -- it looks like a glibc issue to me." But I know I could be completely wrong here, that's why I'm asking :p Let me know what you guys think. If you need/want anything else and I'll get it for you. Thanks. -- David C. Rankin, J.D.,P.E.