Bug 35178 - SIGSEGV in brw_draw_init at brw_draw.c:471 with --enable-shared-dricore
Summary: SIGSEGV in brw_draw_init at brw_draw.c:471 with --enable-shared-dricore
Alias: None
Product: Mesa
Classification: Unclassified
Component: Mesa core (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: mesa-dev
QA Contact:
Depends on:
Reported: 2011-03-10 08:58 UTC by Rui Tiago Matos
Modified: 2018-05-09 05:40 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Description Rui Tiago Matos 2011-03-10 08:58:51 UTC
Program received signal SIGSEGV, Segmentation fault.
    0x011ce9be in brw_draw_init (brw=0x80bf120) at brw_draw.c:471
    471 vbo->draw_prims = brw_draw_prims;
    (gdb) bt
    #0 0x011ce9be in brw_draw_init (brw=0x80bf120) at brw_draw.c:471
    #1 0x011cb5fb in brwCreateContext (api=0, mesaVis=0x80bbb20, driContextPriv=0x80bbca8, sharedContextPrivate=0x0) at brw_context.c:221
    #2 0x011b44b5 in intelCreateContext (api=API_OPENGL, mesaVis=0x80bbb20, driContextPriv=0x80bbca8, sharedContextPrivate=0x0) at intel_screen.c:461
    #3 0x0119e3c3 in dri2CreateNewContextForAPI (screen=0x80b97f8, api=0, config=0x80bbb20, shared=0x0, data=0x8077638) at ../common/dri_util.c:682
    #4 0x0119e41e in dri2CreateNewContext (screen=0x80b97f8, config=0x80bbb20, shared=0x0, data=0x8077638) at ../common/dri_util.c:696
    #5 0x005f79b6 in dri2_create_context (base=0x80775b8, config_base=0x80bc648, shareList=0x0, renderType=32788) at dri2_glx.c:204
    #6 0x005cfe9a in CreateContext (dpy=0x805ca18, generic_id=<value optimized out>, config=0x80bc648, shareList_user=0x0, allowDirect=1, code=24, renderType=32788,
    screen=0) at glxcmds.c:233
    #7 0x005d0151 in glXCreateNewContext (dpy=0x805ca18, fbconfig=0x80bc648, renderType=32788, shareList=0x0, allowDirect=1) at glxcmds.c:1521
    #8 0x004951fe in clutter_backend_glx_create_context (backend=0x8055850, error=0xbfffe4dc) at ./glx/clutter-backend-glx.c:585
    #9 0x004b6323 in _clutter_backend_create_context (backend=0x8055850, error=0xbfffe4dc) at ./clutter-backend.c:410
    #10 0x004d2cb8 in _clutter_feature_init (error=0xbfffe4dc) at ./clutter-feature.c:107
    #11 0x004dfcfb in clutter_init_real (error=0xbfffe4dc) at ./clutter-main.c:1501
    #12 0x004e13b0 in clutter_init (argc=0x0, argv=0x0) at ./clutter-main.c:2008
    #13 0x001e303a in meta_clutter_init () at core/main.c:312
    #14 meta_init () at core/main.c:460
    #15 0x08049e48 in main (argc=1, argv=0xbfffe874) at main.c:425

git blames:

ef58598c1cf2ac689f67c75b2f477f2c404fce98 is the first bad commit
commit ef58598c1cf2ac689f67c75b2f477f2c404fce98
Author: Marek Olšák <maraeo@gmail.com>
Date:   Mon Mar 7 19:34:34 2011 +0100

    vbo: mark vertex arrays as dirty when re-binding
    This fixes:

:040000 040000 86f7e2363cb0c1fc7a146cc36fde9333d0f4bcd1 ca575588faeb8fe79c3d768ff28a7a808a64afac M	src
Comment 1 Rui Tiago Matos 2011-03-10 09:47:34 UTC
BTW, hardware is Intel(R) Ironlake Mobile.
Comment 2 Rui Tiago Matos 2011-03-10 15:58:56 UTC
> git blames:
> ef58598c1cf2ac689f67c75b2f477f2c404fce98 is the first bad commit

Actually that's wrong, I screwed up on that bisect. Sorry. I've run a new bisect and now I'm pretty sure the real culprit is

7d16e2c0cd70dc5a23b746dbc8e44c58366b5353 is the first bad commit
commit 7d16e2c0cd70dc5a23b746dbc8e44c58366b5353
Author: Marek Olšák <maraeo@gmail.com>
Date:   Mon Mar 7 02:03:52 2011 +0100

    mesa: add EXT_texture_compression_latc

BUT, looking at the commit I couldn't see anything related to the backtrace so I remembered I had mesa configured with --enable-shared-dricore and re-configured it without that option: it doesn't crash anymore.
Comment 3 Timothy Arceri 2018-05-09 05:40:20 UTC
This build option was made default with:

commit 2b3a8cbc891894417510fbc72cb108c5835adcf5
Author: Matt Turner <mattst88@gmail.com>
Date:   Fri Jan 13 14:30:36 2012 -0500

    Always build shared dricore
    Tested-by: Eric Anholt <eric@anholt.net>
    Signed-off-by: Matt Turner <mattst88@gmail.com>

So what ever this issue was it was likely fixed long long ago. Closing.

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.