hi Hugo, thanks for the report.
yes, it is known behaviour caused by some scheme garbage collector tricks. you have to use the following gdb options to be able to run fluxus from gdb:Now, for some reason I am unable to run 'gdb' on the fluxus binary, it starts coughing up segmentation faults all over the place like these right after 'run':
handle SIGSEGV nostop noprint handle SIG33 nostop noprint pass handle SIG32 nostop noprint pass put them in a .gdbinit file. best, gabor
