The new shader-db runner segfaults when using Mesa from git, but works fine with my system Mesa (10.4.3). Backtrace: (gdb) run Starting program: /home/cwabbott/code/shader-db/run shaders/ Missing separate debuginfos, use: debuginfo-install glibc-2.20-7.fc21.x86_64 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". ATTENTION: default value of option allow_glsl_extension_directive_midshader overridden by environment. ATTENTION: default value of option shader_precompile overridden by environment. Program received signal SIGSEGV, Segmentation fault. 0x00007ffff3fe3707 in XGetXCBConnection (dpy=dpy@entry=0x6054d0) at x11_xcb.c:9 9 return dpy->xcb->connection; Missing separate debuginfos, use: debuginfo-install elfutils-libelf-0.161-2.fc21.x86_64 elfutils-libs-0.161-2.fc21.x86_64 libXau-1.0.8-4.fc21.x86_64 libdrm-2.4.59-4.fc21.x86_64 libepoxy-1.2-1.fc21.x86_64 libgcc-4.9.2-6.fc21.x86_64 libgomp-4.9.2-6.fc21.x86_64 libpciaccess-0.13.3-0.3.fc21.x86_64 libstdc++-4.9.2-6.fc21.x86_64 libxcb-1.11-3.fc21.x86_64 systemd-libs-216-20.fc21.x86_64 (gdb) bt #0 0x00007ffff3fe3707 in XGetXCBConnection (dpy=dpy@entry=0x6054d0) at x11_xcb.c:9 #1 0x00007ffff41f7014 in dri2_initialize_x11_dri2 (drv=<optimized out>, disp=0x1026fc0) at platform_x11.c:1229 #2 dri2_initialize_x11 (drv=<optimized out>, disp=0x1026fc0) at platform_x11.c:1350 #3 0x00007ffff41f10ca in _eglMatchAndInitialize (dpy=0x1026fc0) at egldriver.c:594 #4 0x00007ffff41f12e4 in _eglMatchDriver (dpy=dpy@entry=0x1026fc0, test_only=test_only@entry=0) at egldriver.c:625 #5 0x00007ffff41ebcd0 in eglInitialize (dpy=0x1026fc0, major=0x0, minor=0x0) at eglapi.c:464 #6 0x0000000000401b15 in main (argc=2, argv=0x7fffffffdd68) at run.c:290
Turns out I was missing --enable-gbm --with-egl-platforms=x11,drm when running ./configure (thanks Matt!).
FWIW you don't actually need --enable-gbm - that happens automatically if you have --with-egl-platforms=x11,drm
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.