Here is how an interpreter segfaults without doing anything except parsing an include file.
Make the C sources of the Interpreter on a i86 - 32bit system but make sure it is prepared for 64-bit build. Take those C sources and upload them to a 64-bit system. Try to compile using \-\-without-euphoria switch. You can get an interpreter. Once built though, all but the most trivial programs crash and burn.
Why does this happen? When reading the constants in one of the include files, the integers overflow in size and there is no check generated to see whether the value is still an integer or not. The interpreter has decided to optimize this check away and I think it has something to do with going from 32-bit to 64-bit.