hi.

a lot of this email deals with how to log.

the interesting part however, is that i found the source of the problem (even without logs): the jpg's provided in 10.glsl are actually broken, i guess because of wrong line-feeds due to CVS' auto linefeed conversion. (you can easily check by trying to open the jpg's with your favourite viewer)

so the fix for the crashes is to use working jpegs :-)

one option is to re-download the package (https://gem.iem.at/releases/0.91/gem-CVS20080411-W32-i686-bin-doc.zip) where i have (hopefully) fixed the jpg.

another option is the latest Pd-extended, that has already the recent binaries with seemingly fixed images.

pat@mamalala.org wrote:

IOhannes m zmoelnig zmoelnig@iem.at a écrit :

...

the solution above runs in the ordinary w32shell "cmd" (i don't have such fancy stuff like cygwin on w32)

on mssys:

$ /c/pd/bin/pd.com -stderr -open 01_simple_texture.pd 2> crash.log $ cat crash.log socket receive error: Unknown error (10054)

now what again was the reason to use the cygshell (or mssys shell)? i can create logs just fine here using the ordinary "cmd".

$ rm img1.jpg #now I can open the patch

$ /c/pd/bin/pd.exe -open 01_simple_texture.pd 2> crash.log $ cat crash.log pd_gui: pd process exited closing audio... closing MIDI... ... done.

actually it doesn't look that bad; you just forgot the "-stderr" flag in order to not print to the pd-console but to the log. anyhow, the interesting thing would be the lines before "pd process exited"

mfg.adsr IOhannes