Hi,

in a discussion with IOhannes at LAC he asked me to try the multiple_window branch of Gem to see if this crashes Gem with newer Mesa free drivers as well. I now did so and it crashes, too. This is with Debian's 6.5.1-0.5 drivers. I didn't test the 6.5.2 branch, as last time I did, it wasn't rendering anything at all but still crashing with normal Gem.

(Btw: The new Ubuntu Feisty comes with mesa 6.5.2, the new stable Debian has 6.5.1, so the number of people may increase who experience the crash/no rendering issue, if they upgrade and have chipsets using the free Mesa drivers like for Intel chips.)

Here's a bit of logging/gdb output when doing [create, 1( and then [0, destroy(:

Direct Rendering enabled! destroy A destroy B destroy C destroy D destroy E destroy F destroy F

Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1211517248 (LWP 24805)] 0xb54f0af0 in ?? () (gdb) bt #0 0xb54f0af0 in ?? () #1 0xb7765d1c in glXDestroyContext () from /usr/lib/libGL.so.1 #2 0xb7767e40 in glXMakeCurrentReadSGI () from /usr/lib/libGL.so.1 #3 0xb77680d3 in glXMakeCurrent () from /usr/lib/libGL.so.1 #4 0xb7b7dbd5 in gemwindow::destroyMess () from /usr/lib/pd/extra/Gem/Gem.pd_linux #5 0xb7b7d734 in gemwindow::destroyMessCallback () from /usr/lib/pd/extra/Gem/Gem.pd_linux #6 0x0809fd15 in pd_typedmess (x=0x88, s=0x80, argc=0, argv=0x810e750) at m_class.c:728 Previous frame inner to this frame (corrupt stack?)

Ciao