Re: [i3] segfaults with libxcb-1.10
>"MC" == Marcus Crestani writes: MC> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread MC> 0 ??? 0x0001 0 + 4294967296 MC> 1 libxcb.1.dylib 0x000110152f24 get_socket_back + 139 MC> 2 libxcb.1.dylib 0x0001101534ae xcb_send_request + 935 MC> 3 libxcb.1.dylib 0x000110159784 xcb_intern_atom + 197 MC> 4 libstartup-notification-1.0.dylib 0x00010fd3d37e sn_xcb_display_new + 78 MC> 5 i3 0x00010f6d4e30 main + 4000 MC> 6 libdyld.dylib 0x7fff906185fd start + 1 MC> Has anybody else seen this problem with libxcb-1.10 on OS X or other MC> platforms? Is this most likely caused by XQuartz, libxcb, libsn, or i3? Since nobody seems to have run into this problem, I started digging deeper. The problem was caused by my setup, I realized that I was linking against libsn that itself was linking against a rather old libxcb-1.6. Rebuilding libsn and linking it against libxcb-1.10 fixed the problem. Sorry for the noise. -- Marcus
[i3] segfaults with libxcb-1.10
I am using i3 on OS X 10.9.3 as the window manager under XQuartz. Newest XQuartz 2.7.6 updated (amongst many other parts) libxcb to version 1.10 (previous versions came with libxcb-1.9.1). With libxcb-1.10, i3 (latest release, master, and next) segfaults during startup in libxcb: Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 ??? 0x0001 0 + 4294967296 1 libxcb.1.dylib 0x000110152f24 get_socket_back + 139 2 libxcb.1.dylib 0x0001101534ae xcb_send_request + 935 3 libxcb.1.dylib 0x000110159784 xcb_intern_atom + 197 4 libstartup-notification-1.0.dylib 0x00010fd3d37e sn_xcb_display_new + 78 5 i3 0x00010f6d4e30 main + 4000 6 libdyld.dylib 0x7fff906185fd start + 1 Has anybody else seen this problem with libxcb-1.10 on OS X or other platforms? Is this most likely caused by XQuartz, libxcb, libsn, or i3? Thanks, -- Marcus
