search for: waitforexit

...d you run j3 in gdb and get me a backtrace? Sure: (gdb) bt #0 0x950be44e in __semwait_signal () #1 0x950e93e6 in _pthread_cond_wait () #2 0x950e8dcd in pthread_cond_wait$UNIX2003 () #3 0x000be2d2 in mvm::Cond::wait (this=0x20527c4, l=0x2052790) at ctlock.cpp:151 #4 0x00020137 in j3::Jnjvm::waitForExit (this=0x20525a8) at Jnjvm.cpp: 1225 #5 0x00001cf6 in main (argc=4, argv=0xbffff070, envp=0xbffff084) at Main.cpp:47 I'll try installing VMKit in a virtual Linux for comparison. Konrad.

...t; > Sure: > > (gdb) bt > #0 0x950be44e in __semwait_signal () > #1 0x950e93e6 in _pthread_cond_wait () > #2 0x950e8dcd in pthread_cond_wait$UNIX2003 () > #3 0x000be2d2 in mvm::Cond::wait (this=0x20527c4, l=0x2052790) at > ctlock.cpp:151 > #4 0x00020137 in j3::Jnjvm::waitForExit (this=0x20525a8) at Jnjvm.cpp:1225 > #5 0x00001cf6 in main (argc=4, argv=0xbffff070, envp=0xbffff084) at > Main.cpp:47 > > I'll try installing VMKit in a virtual Linux for comparison. > > Konrad. > > -------------- next part -------------- An HTML attachment was scrubbe...

...jvm*, j3::Class*, ...) () #4 0x00000000005cb662 in j3::Jnjvm::asciizToStr(char const*) () #5 0x00000000005cbde4 in j3::Jnjvm::CreateArithmeticException() () #6 0x00007ffff7f6316d in ?? () #7 0x0000000000000000 in ?? () The main thread was waiting in "vmkit::VirtualMachine::waitForExit() ()", so the application (HelloWorld) should have been started. 1. To me, the stack trace seems not showing where the original error happened. It seems an arithmetic error happened somewhere, VM was trying to throw an exception, but met another error. Is this correct? And how can I track...

...read_start () Thread 1 (process 14442 local thread 0x2e03): #0 0x950be44e in __semwait_signal () #1 0x950e93e6 in _pthread_cond_wait () #2 0x950e8dcd in pthread_cond_wait$UNIX2003 () #3 0x000be2d2 in mvm::Cond::wait (this=0x20527c4, l=0x2052790) at ctlock.cpp:151 #4 0x00020137 in j3::Jnjvm::waitForExit (this=0x20525a8) at Jnjvm.cpp: 1225 #5 0x00001cf6 in main (argc=4, argv=0xbffff070, envp=0xbffff084) at Main.cpp:47 In the meantime I installed VMKit under Linux, where it works perfectly well for most applications I tried. However, I managed to crash it once: > j3 -cp clojure-1.1.0...

...ss*, ...) () > #4 0x00000000005cb662 in j3::Jnjvm::asciizToStr(char const*) () > #5 0x00000000005cbde4 in j3::Jnjvm::CreateArithmeticException() () > #6 0x00007ffff7f6316d in ?? () > #7 0x0000000000000000 in ?? () > > The main thread was waiting in "vmkit::VirtualMachine::waitForExit() ()", so > the application (HelloWorld) should have been started. > > 1. To me, the stack trace seems not showing where the original error > happened. It seems an arithmetic error happened somewhere, VM was trying to > throw an exception, but met another error. Is this correct?...

Hmm, I am not getting that error message on my MacOS 10.5 machine with that same gcc. Could you run j3 in gdb and get me a backtrace? Thanks! Nicolas On Tue, Apr 6, 2010 at 9:23 PM, Konrad Hinsen <konrad.hinsen at fastmail.net>wrote: > Hi Nicolas, > > > Did you compile vmkit with llvm-gcc or gcc? Did you make sure the path to >> GNU Classpath is correct in your

Hi Nicolas, > Did you compile vmkit with llvm-gcc or gcc? Did you make sure the > path to GNU Classpath is correct in your configure command? I let the configure script of VMKit do its work and it decided to use gcc, the gcc 4.0.1 that is part of Apple's XCode distribution for MacOS 10.5. There is no llvm-gcc anywhere on my machine. Should I have one? I did install llvm without

...14442 local thread 0x2e03): > > #0 0x950be44e in __semwait_signal () > #1 0x950e93e6 in _pthread_cond_wait () > #2 0x950e8dcd in pthread_cond_wait$UNIX2003 () > #3 0x000be2d2 in mvm::Cond::wait (this=0x20527c4, l=0x2052790) at > ctlock.cpp:151 > #4 0x00020137 in j3::Jnjvm::waitForExit (this=0x20525a8) at Jnjvm.cpp:1225 > #5 0x00001cf6 in main (argc=4, argv=0xbffff070, envp=0xbffff084) at > Main.cpp:47 > > > > In the meantime I installed VMKit under Linux, where it works perfectly > well for most applications I tried. However, I managed to crash it once: &gt...