Thanks for the quick answer Iohannes,

You guessed right: I do use N-Vidia's non free drivers (plain linux kernel nv drivers giving poor OpenGL results) and the latest c++ compiler from unstable.

Is there a workaroud?

You seem to infer so in the bug-report page but I don't quite get it... Is it enough just to try and compile Gem with another (earlier version) of gcc/g++?

I'm not so confident about how to do it anyway but if it's a solution, I can try it (-:

++

Jé

zmoelnig@iem.at a écrit :

Zitat von Jerome Tuncer columbiatwo@free.fr:

...

Hello list...

Don't if it's the right place to post for such a thing, sorry if not...

I run Pd 0.40-test7 on Debian Linux and when loading most of Gem's pix_ objecs help I get an error in the term running pd which locks all of pd functions : menus are still available but do not execute any actions when clicked...

The error is of the form :

*** glibc detected *** free(): invalid pointer: 0xa5d2fb68 ***

Except that the pointer varies from times to times of course...

As stated I only get the crash with pix_* objects' help patches. Instantiating the objects themselves in a blank window doesn't seem to cause any problems...

Any ideas on where it can come from?

yes, this is a known issue on debian/testing systems. unfortunately it is not a bug in Gem but rather a problem with the combination of libstdc++ and nvidia-drivers (i guess you are using them)

Gem uses exception-handling for various errors, like not being able to load an image with [pix_image] or not finding a FreeFrame-plugin. the above mentioned bug crashes applications which throw an error (even though it gets caught)

this bug is already filed in the debian bug-tracker, though it doesn't seem to be high-priority. there are some workarounds, which you can find at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=364907

mfg,asdr IOhannes