search for: core__init

...ile bootstraping VM That looks like a JNI issue. > About the SIGSEGV you get with clojure.jar, I ran the code and got > the same error. After investigation, it turns out that the methods > you have in that .jar are quite big (50,000 bytecodes) and the > static initializer of the core__init class just crashes LLVM because > the stack of the thread is not big enough. That's indeed a big one. It's the initialization of the standard library of a Lisp implementation. > I hate Java bytecode generators :) I like them. They let me use all those nice Java libraries withou...

...get that UnsatisfiedLinkError. You have made symlinks of GNU Classpath libraries with the .so suffix. Since you're on MacOS, you should do symlinks with the .dylib suffix (I notice that I'm not saying that on the webpage, I'll fix that right now). I'm not sure what to do about that core__init function. I will try to create a bigger stack to see if that changes anything or if LLVM inifinite loops. Cheers, Nicolas On Sat, Apr 10, 2010 at 9:09 PM, Konrad Hinsen <konrad.hinsen at fastmail.net>wrote: > Hi Nicolas, > > > I have added some diagnostic message when failin...

...suffix. Since > you're on MacOS, you should do symlinks with the .dylib suffix (I > notice that I'm not saying that on the webpage, I'll fix that right > now). Thanks - that did it! All my tests now run just like under Linux. > I'm not sure what to do about that core__init function. I will try > to create a bigger stack to see if that changes anything or if LLVM > inifinite loops. I am rather surprised that the size of a method should have an impact on stack usage, but then I haven't looked at all at how VMKit works yet. That's my next project...

...y in the bootstrap in the VM. Please svn up and let me know what it prints. About the SIGSEGV you get with clojure.jar, I ran the code and got the same error. After investigation, it turns out that the methods you have in that .jar are quite big (50,000 bytecodes) and the static initializer of the core__init class just crashes LLVM because the stack of the thread is not big enough. I hate Java bytecode generators :) Nicolas On Fri, Apr 9, 2010 at 9:26 PM, Konrad Hinsen <konrad.hinsen at fastmail.net>wrote: > On 09.04.2010, at 11:28, nicolas geoffray wrote: > > VMKit runs multiple th...

On 09.04.2010, at 11:28, nicolas geoffray wrote: > VMKit runs multiple threads (for example for GC, finalization, etc), > so I need the back trace of other threads as well :) Here it comes: Thread 4 (process 14442 thread 0x2003): #0 0x950be44e in __semwait_signal () #1 0x950e93e6 in _pthread_cond_wait () #2 0x950e8dcd in pthread_cond_wait$UNIX2003 () #3 0x000be2d2 in mvm::Cond::wait

On Sun, Apr 11, 2010 at 7:12 PM, Konrad Hinsen <konrad.hinsen at fastmail.net>wrote > > I'm not sure what to do about that core__init function. I will try to >> create a bigger stack to see if that changes anything or if LLVM inifinite >> loops. >> > > I am rather surprised that the size of a method should have an impact on > stack usage, but then I haven't looked at all at how VMKit works yet. That...