Could you try to run the command inside gdb then send me the backtrace ?
neko used over 2G process memory (on my 512M machine) under gdb,
and took 20 minutes to produce this stack trace.
Is it typical for neko compilations to use that much RAM, or is it a
symptom of a problem? Can neko be run in interpreted mode (without JIT)
or be forced to collect garbage more frequently?
This is a symptom of the problem. Looks like the neko_module_jit method
start an infinite loop that allocates memory when compiled with -O3 on
your OS. Could you try to investigate the sources in neko/vm/jit_x86.c
and check what is going wrong ?
You can reproduce this neko 1.6.0 build segfault by compiling with gcc 4.1.1
using -O1 or higher and gc6.8 or gc-7.0. I don't know if the problem is with
the jit or the gc.
gcc 4.2.1 is fine on any optimization level.
Does Neko have an interpreted (non-jit) mode?
Yes, you need to run with -interp
But in that case it seems that the error does not seems to occur in the
JIT'ed code but while the neko module JIT code is produced. Try to
disable the JIT_ENABLE define in neko/vm/jit_x86.c to completely
disactivate the jit.
Nicolas
--
Neko : One VM to run them all
(http://nekovm.org)
