Bug#982661: mame: Crash on startup

[Bernhard Übelacker]

Hello Celelibi,
unfortunately, if I try to reproduce I reach the exact same stack,
but in case of my VM ctx->pipe->set_shader_buffers contains a
valid function pointer.

Maybe you could add some information about which graphics card
you use and maybe running with 'export LIBGL_DEBUG=verbose'
might give some hints.

Do you see such issues with other hardware accelerated programs too?

Another way would be to debug the function where this function
pointer initially gets set and if it gets overwritten later
by a wrong memory operation by a watchpoint.
In my test it gets set when a context gets created in [1].

Kind regards,
Bernhard

[1]
     ...
     #1  0x00007ffff0b0905c in st_api_create_context () at ../src/mesa/state_tracker/st_manager.c:917
     #2  0x00007ffff0afd6c2 in dri_create_context () at ../src/gallium/frontends/dri/dri_context.c:163
     #3  0x00007ffff0ffccab in driCreateContextAttribs () at ../src/mesa/drivers/dri/common/dri_util.c:480
     #4  0x00007ffff0ffce1e in driCreateNewContextForAPI () at ../src/mesa/drivers/dri/common/dri_util.c:510
     #5  driCreateNewContext () at ../src/mesa/drivers/dri/common/dri_util.c:518
     #6  0x00007ffff2377535 in dri2_create_context () at ../src/glx/dri2_glx.c:216
     #7  0x00007ffff2366938 in CreateContext () at ../src/glx/glxcmds.c:342
     #8  0x00007ffff2366d2e in glXCreateContext () at ../src/glx/glxcmds.c:467
     #9  0x00007ffff579e983 in glXCreateContext () at ../src/GLX/libglx.c:246
     ...