Friday, February 3, 2006, 11:42:08 AM, Nicolas Cannasse wrote: > In order to check that it's actually a bug inside a GC call, could you > wrap calls in "alloc.c" with printf before/after ? Maybe only needed in > the case of alloc_object if you crash on a $new call.
Argh! I just discovered that all my recent efforts have been for naught. Putting printf()s inside the macros in interp.c causes a crash because gcc is confused by the call to stdio with global registers allocated. If I remove my printf()s I am back to... (cd src; LD_LIBRARY_PATH=../bin: NEKOPATH=../boot:../bin ../bin/neko nekoml -v neko/Main.nml nekoml/Main.nml) try: nekoml.n try: ..\bin/nekoml.n -1 try: ..\boot/nekoml.n 0 try: std.ndll try: ..\bin/std.ndll 0 Parsed core/Core.nml Typing Core.magic Typing Core.throw Typing Core.assert Typing Core.invalid_arg Typing Core.error Typing Core.ignore Typing Core.fst Typing Core.snd Typing Core.int Typing Core.ord Typing Core.chr Typing Core.string Typing Core.nstring Typing Core.print Typing Core.nprint Typing Core.compare Typing Core.min Typing Core.max Typing Core.sprintf Typing Core.printf Typing Core.stream Typing Core.stream_token Typing Core.stream_junk Typing Core.stream_pos Typing done with core/Core.nml Compiling Core.n make: *** [compiler] Error 5 gdb just says Program exited with code 01. e -- Neko : One VM to run them all (http://nekovm.org)
