similar to: [LLVMdev] Issues with HelloWorld on VMKit

Hi Matteo, Matteo Migliavacca wrote: > HI I tried to follow the procedure at http://vmkit.llvm.org/get_started.html > . > > OK. Which cpu/os target? > Builds of LLVM and classpath went fine (after fixing a few dependency > problems). > > After compiling a simple HelloWorld with javac I got > > ../vmkit/Debug/bin/jnjvm HelloWorld > > hang for a while and

Hi Nicholas, and thanks for the prompt reply... On 20 Aug 2009, at 15:28, Nicolas Geoffray wrote: > Matteo Migliavacca wrote: >> HI I tried to follow the procedure at http://vmkit.llvm.org/get_started.html > > OK. Which cpu/os target? It was x86/linux... >> Builds of LLVM and classpath went fine (after fixing a few dependency >> problems). >> >> After

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

VMKit runs multiple threads (for example for GC, finalization, etc), so I need the back trace of other threads as well :) Thanks! Nicolas On Fri, Apr 9, 2010 at 9:28 AM, Konrad Hinsen <konrad.hinsen at fastmail.net>wrote: > On 7 Apr 2010, at 21:36, nicolas geoffray wrote: > > Hmm, I am not getting that error message on my MacOS 10.5 machine with >> that same gcc. Could you

On 7 Apr 2010, at 21:36, nicolas geoffray wrote: > 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? 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,

I'm trying to build the SVN version of VMKit and I'm getting this error while building. I have llvm and clang built from SVN too. Any help? llvm[2]: Building Release+Asserts mmtk-vmkit.jar all vmjc: JavaClass.cpp:442: j3::JavaObject *j3::Class::doNew(j3::Jnjvm *): Assertion `this && "No class when allocating."' failed. 0 vmjc 0x0000000000e9c44f 1 vmjc

Are you running on 64bit (your backtrace addresses suggest you are)? I'm encountering the same error when trying to use VMKit on 64bit, which I believe is an unsupported target. ~Will On Tue, Aug 23, 2011 at 5:17 PM, Frederic Perez Ordeig <fredericp at gmail.com> wrote: > I'm trying to build the SVN version of VMKit and I'm getting this error > while building. > I

Hmm, disregard my previous comment (while you might still have issues with 64bit, that's not what's primarily causing your issue)--your particular error is when you don't point vmkit to the classpath libraries properly. Set it with the configure option --with-gnu-classpath-glibj=/path/to/classpath-0.97.2/lib/glibj.zip Good luck! ~Will On Tue, Aug 23, 2011 at 5:49 PM, Will Dietz

Ah yes, thanks, this was one problem, now I hit another: llvm[2]: Building Release+Asserts mmtk-vmkit.jar all Thread 0x110000000 received a SIGSEGV: either the VM code or an external native method is bogus. Aborting... ; 0x5cfeed (0x1100fe410) in _Z14sigsegvHandleriP7siginfoPv ; 0x2b889c232c60 in Unknown method ; 0x561499 (0x1100fe900) in _ZN2j310JavaObject7acquireEPS0_ ; 0x55b464 (0x1100fe920)

Hi Nicolas, I'm running it on Kubuntu. Now that you mention it I did have a problem during vmkit setup. After running the ./configure file with all the options I ran the make file it was giving this error: make[3]: *** [/.automount/root/exports/transient/nataraj/Project/vmkit-0.25/lib/Mvm/Runtime/Release/EscapeAnalysis.o] Error 1 " So I went into Makefile.common and modified GNU

Hi, I replaced the MMTk code with a C-version MMTk code (I have been working on such AOT compiler for a while). The compiler should deal with most of the MMTk code base correctly - at least I get marksweep running with a tiny client). So I am trying to put the C version MMTk back with VmKit. I tried not to change much existing code except where necessary, such as name mangling and MMTkObject

Thanks Nicolas, Gaël I followed your instructions and installed compatible versions of llvm, vmkit and GNU Classpath also I unzipped glibj.zip and pointed GNU Classpath lib variable to the the unzipped files during vmkit configure. That error has vanished. Now when I run jnjvm or vmkit in Release/bin on any file I'm getting a new error : " terminate called without an active exception

Hi Nataraj, You're using incompatible versions of vmkit and GNU Classpath. First, you should use vmkit 0.26 and llvm 2.6 (at least, -- use trunk if there are problems). Second, you should use GNU Classpath 0.97.2. Good luck! Nicolas Nataraj Sundar wrote: > Hi Nicolas, > > I'm running it on Kubuntu. > > Now that you mention it I did have a problem during vmkit setup.

Hi Konrad, I have added some diagnostic message when failing that early 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

Hi, I intent to use VMKIT to convert java byte codes to LLVM IR I have installed VMKIT 0.26, on running jnjvm (as ./jnjvm Hello.class) in Release/bin I get the same error irrespective of class content : jnjvm: JavaClass.cpp:469: jnjvm::JavaObject* jnjvm::Class::doNew(jnjvm::Jnjvm*): Assertion `(this->isInitializing() || classLoader->getCompiler()->isStaticCompiling()) &&

Hi, I've managed to compile it the class down to a native executable. However, the executable runs for a while then spits out: terminate called without an active exception Aborted and dies. The program never gets to the normal output. Here is a stack trace from gdb: #0 0xf3f6baa6 in raise () from /lib/libc.so.6 #1 0xf3f6d3a8 in abort () from /lib/libc.so.6 #2 0xf41918f8 in

Hi Nataraj, Which platform are you running on? Did you follow all the steps on vmkit.llvm.org getting started page, especially for GNU Classpath? Thanks! Nicolas Nataraj Sundar wrote: > Hi, > > I intent to use VMKIT to convert java byte codes to LLVM IR > > I have installed VMKIT 0.26, on running jnjvm (as ./jnjvm > Hello.class) in Release/bin I get the same error

Have you created the symbolic links to GNU Classpath .so? ie step 2 of http://vmkit.llvm.org/get_started.html? Nicolas Nataraj Sundar wrote: > Thanks Nicolas, Gaël > > I followed your instructions and installed compatible versions of llvm, > vmkit and GNU Classpath also I unzipped glibj.zip and pointed GNU > Classpath lib variable to the the unzipped files during vmkit

Hello, Here's a tiny patch to the VMKIT tools makefile, that allows you to build VMKIT without both Java and CLI. I'm working on a new bytecode front end so wanted a 'clean' mvm without building to two existing front ends. Currently it still tries to build VMJC even when its told not to build the JNJVM. This patch fixes that. Index: tools/Makefile

Yes I did, one thing worth mentioning is on running configure for GNU Classpath towards the end this error is displayed and it crashes, I assumed it was okay and went to create the symbolic links and completed the rest of the process with vmkit mentioned in Getting Started as instructed: -I../../../native/jni/native-lib -W -Wall -Wmissing-declarations -Wwrite-strings -Wmissing-prototypes