Building Neko 1.7.1 clean (no previous version installed, fresh from the
tarfile) I get an interpreter that inserts an annoying message in front
of each and every invocation of it:


        GC Warning: USE_PROC_FOR_LIBRARIES + GC_LINUX_THREADS performs poorly.


The unfortunate problem here is that I cannot find either of those flags
anywhere in the source tree:


        $ find -type f | xargs grep GC_LINUX_THREADS
        $ find -type f | xargs grep BeginCall
        ./vm/interp.c:#define RuntimeError(err,param)   { if( param ) pc++; 
PushInfos(); BeginCall(); val_throw(alloc_string(err)); }
        ./vm/interp.c:                                  pc++; PushInfos(); 
BeginCall(); \
        ./vm/interp.c:#define BeginCall() \
        ./vm/interp.c:          BeginCall();
        ./vm/interp.c:          BeginCall(); \
        ./vm/interp.c:                  BeginCall(); \
        ./vm/interp.c:                          BeginCall();
        ./vm/interp.c:                  BeginCall();
        ./vm/interp.c:                  BeginCall();
        ./vm/interp.c:                                  BeginCall();
        ./vm/interp.c:          BeginCall();
        ./vm/interp.c:          BeginCall();
        ./vm/interp.c:                  BeginCall();
        ./vm/interp.c:          BeginCall();


You will note that with the second use of find/xargs/grep I can find a
known string like "BeginCall" so I'm pretty sure that's working.  So I
have a two-part question:

     1. How, exactly, are the error strings for that message being
        generated and yet not findable with grep?
     2. What, exactly, do I do to get those messages to stop from
        appearing each and every time I invoke the Neko runtime?


-- 
Michael T. Richter <[EMAIL PROTECTED]> (GoogleTalk:
[EMAIL PROTECTED])
It's OK to figure out murder mysteries, but you shouldn't need to figure
out code. You should be able to read it. (Steve McConnell)
-- 
Neko : One VM to run them all
(http://nekovm.org)

Reply via email to