Can you say more about the crash, perhaps something along the lines of a stack trace?
I'm not sure if it's helpful, but here it is from OS X: Seg fault (internal error) at 0xb7 Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_PROTECTION_FAILURE at address: 0x000000b7 0x005d4ee0 in compile_k () (gdb) backtrace #0 0x005d4ee0 in compile_k () #1 0x005f2a1e in scheme_top_level_do_worker () #2 0x005f2c48 in scheme_top_level_do () #3 0x005d581a in scheme_compile_for_eval () #4 0x005dd064 in scheme_eval_multi () #5 0x005dd286 in do_eval_string_all () #6 0x0000a51d in std::string::_M_rep () at /usr/include/c++/4.2.1/bits/basic_string.h:243 #7 0x0000a51d in ~basic_string [inlined] () at /usr/include/c++/4.2.1/bits/basic_string.h:493 #8 0x0000a51d in fluxus::Interpreter::Interpret (str=@0xbffff064, ret=0x0, abort=true) at src/Interpreter.cpp:243 #9 0x0000abdb in std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> >::_M_rep () at /usr/include/c++/4.2.1/bits/basic_string.h:162 #10 0x0000abdb in ~basic_string [inlined] () at /usr/include/c++/4.2.1/bits/basic_string.h:493 #11 0x0000abdb in fluxus::Interpreter::Initialise () at basic_string.h:162 #12 0x00015ced in run (data=0xbffff718) at src/main.cpp:270 #13 0x0058fbd1 in scheme_main_stack_setup () #14 0x00014166 in main (argc=1, argv=0xbffff750) at src/main.cpp:437
I wonder whether Fluxus might accidentally call Racket API functions in a OS thread other than one that was used to initialize Racket.
I'm not sure, as far as I know it does not, but we have to investigate this. Thanks for your help. _________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/users
