similar to: [LLVMdev] vmkit segmentation fault revision 107990

Hi All, Thanks Nicolas for pointing out that I needed --enable-targets=x86,cpp for my llvm config to get vmkit to build. The process gets a lot farther but fails in different places depending upon the vmkit config (Can you please see the three case below?). My machine is a intel core i7 running ubuntu karmic and gcc 4.4.1. What arch/OS/distro/gcc do you all have VMKit working on? thanks for

Hi Nicolas, I'm trying now to build vmkit with mmtk: ./configure --with-llvmsrc=/home/zoewolk/RESEARCH/llvm --with-llvmobj=/home/zoewolk/RESEARCH/llvm --with-gnu-classpath-glibj=/home/zoewolk/RESEARCH/classpath-0.97.2/lib --with-gnu-classpath-libs=/home/zoewolk/RESEARCH/classpath-0.97.2/lib --with-gc=mmtk I've built llvm-gcc from source and configured llvm so that it can find it.

Thanks Nicolas for your help with my build problems with vmkit. Yes, I was missing ant -- great catch (I'm on a newly installed machine). That fix with this configuration, gets me to the error below. Any thoughts (build tools, other I may be missing that are not checked for)? Are there steps that you suggest I try to gather more information on the problem? Also -- it seems to be building

Hi Zoe, maybe you've already solved your problem with VMKit configuration, but here you can find a mini-tutorial that I've done to guide people on VMKit installation. http://www2.dcc.ufmg.br/laboratorios/llp/wiki/doku.php?id=afpf Best regards, Alysson On Wed, Jun 30, 2010 at 1:34 PM, nicolas geoffray < nicolas.geoffray at gmail.com> wrote: > Hi Zoe, > > Unfortunately, I

Hi Zoe, Unfortunately, I don't have access to a x64 machine anymore, so I can't test that architecture on vmkit. Could you install a virtual machine on your machine that is x86_32? I know it has been successfully built and ran on x86_32 on different systems. Cheers, Nicolas On Wed, Jun 30, 2010 at 7:49 AM, Zoe Wolk <zoewolk at gmail.com> wrote: > Hi again Nicolas, > >

Hi All, Has vmkit been updated and tested with LLVM 2.8? I am unable to build it (llvm builds fine). There were some errors with Makefile.rules: $(Verb) $(LLVMAS) -f $(<F) -o - | $(LLC) -march=cpp -cppgen=contents -o $@ (march and cppgen options not recognized). What I cannot get past is this one (the warnings concern me as well): ... make[3]: Leaving directory

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)

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

Hi Frederic, On Wed, Aug 24, 2011 at 11:01 AM, Frederic Perez Ordeig <fredericp at gmail.com > wrote: > 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

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

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

Hi Sergii, I think there is a problem in your configure command for VMKit. If you look at what you provide for glibj: --with-gnu-classpath-glibj="/home/svozniuk/llvm/classpath-0.97.2 I don't think it's right. You should change it to: --with-gnu-classpath-glibj="/home/svozniuk/llvm/classpath-0.97.2/lib/glibj.zip Also please make sure that you have created the links for the

Thanks Alysson. Unfortunately, those instructions don't work for me (I followed them exactly using a clean system) -- probably because of the recent changes to the svn heads. After fixing EscapeAnalysis in vmkit to use the updated CallInst.getArgOperand interface I hit the error below. I was interested in using mmtk with the system (as recommended), but that requires a llvm-gcc build (and

Hi, Nicolas Indeed, I did not have ant installed and installing it allowed me to overcome the previous error. However the next one appeared. I have ran make with ENABLE_OPTIMIZED=1 VERBOSE=1 and here is the output (the last part of it) make[2]: Entering directory `/home/svozniuk/llvm/vmkit/mmtk/java' /usr/bin/ant -buildfile /home/svozniuk/llvm/vmkit/mmtk/java/build.xml Buildfile:

Hi Akshat, Please use version 0.97.2. vmkit does not support 0.98. Also, it should be fine to not compile gtk+ peer. Nicolas On Mon, Aug 29, 2011 at 8:58 PM, Akshat Gupta <g.akshat at gmail.com> wrote: > Thanks Nicolas, > I do have --with-gnu-classpath-libs and --with-gnu-classpath-glibj > pointing to the right thing, but I have gnu class path 0.98 instead of 0.97 > and its

Thanks Nicolas, I do have --with-gnu-classpath-libs and --with-gnu-classpath-glibj pointing to the right thing, but I have gnu class path 0.98 instead of 0.97 and its the non X version. So I do not have the libgtkpeer.so. Maybe that is the reason why it is crashing. Unfortunately, I am not able to compile GNU class path with gtk+ peer right now. Will give it a try on the mac. Thanks, Akshat

Hi all, I am trying to build VMKit on Linux/x86 and I got error messages like below, llvm[1]: Linking Debug+Asserts executable vmjc /root/llvm/vmkit/tools/vmjc/Debug+Asserts/vmjc.o: In function `mvm::SpinLock::acquire()': /root/llvm/vmkit/include/mvm/Threads/Locks.h:164: undefined reference to `__sync_val_compare_and_swap_4' /root/llvm/vmkit/include/mvm/Threads/Locks.h:168: undefined

Hi, I just did a reconfigure and rebuild with the latest svn for vmkit code. The code still seg faults but the stack trace seems to have changed. llvm[2]: Building Debug+Asserts mmtk-vmkit.jar all vmjc: JavaRuntimeJIT.cpp:172: uint32 j3VirtualTableLookup(j3::Class*, uint32, uint32*, j3::JavaObject*): Assertion `dmeth->classDef->isInitializing() && "Class not ready in a virtual

This error usually shows up when vmkit cannot find the classpath libs and jar. Make sure --with-gnu-classpath-libs points to the directory of .so files are, and that --with-gnu-classpath-glibj points to glibj.zip. Nicolas On Sat, Aug 27, 2011 at 5:13 AM, Akshat Gupta <g.akshat at gmail.com> wrote: > Hi, > I just did a reconfigure and rebuild with the latest svn for vmkit code. >

Hi all, I haven't found this trick anywhere (including llvm/docs/MakefileGuide.html) so it maybe useful. This occurs only in 64 bit version of linux, linker of 32 bit system understands everything correctly. Situation: While building, at link stage, a 64bit version of some executable, with several archive libraries, say, A.a, B.a, C.a build fails with some "undefined reference to