+ am i right in thinking that chuck doesn't function (yet) in a 64bit environment? it compiles, but segfaults.
wondering this as well. as i switched directly from win32 to linux-amd64, and remember getting the mandolin example to play once, and see in the 1.1.4.8 changelog: "corrected more issues on some 64-bit systems", and some of the examples will run without crashing (eg time/arrays), i think theres some degree of planning for 64bit compatiblity in the original design (unlike say, Pure-Data or SuperCollider).. a few odd looking things - 0x0, and some of those <self>s should probably be pointer size - (not a scientist).. m stereo # gdb chuck (gdb) set args curly2.ck (gdb) run Starting program: /usr/bin/chuck curly2.ck Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 47838618508944 (LWP 3022)] 0x00000000004cbcde in impulse_ctor (SELF=0x0, ARGS=<value optimized out>) at ugen_xxx.cpp:1018 1018 OBJ_MEMBER_UINT( SELF, impulse_offset_data ) = (t_CKUINT)new Pulse_Data; (gdb) where #0 0x00000000004cbcde in impulse_ctor (SELF=0x0, ARGS=<value optimized out>) at ugen_xxx.cpp:1018 #1 0x00000000004163d5 in Chuck_Instr_Func_Call_Member::execute (this=0x6d4670, vm=<value optimized out>, shred=0x869d30) at chuck_instr.cpp:2271 #2 0x0000000000411d6a in Chuck_VM::compute (this=0x6d9770) at chuck_vm.cpp:1416 #3 0x0000000000411fac in Chuck_VM::run (this=0x6d9770) at chuck_vm.cpp:555 #4 0x0000000000454aff in main (argc=2, argv=0x7fff5fc1be28) at chuck_main.cpp:621 i suppose its just some kind of bug :)