similar to: [LLVMdev] VMKit link

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 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

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

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 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

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 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

For anyone who encounters this issue in the future, my issue was the configuration of llvm-gcc. Configure with --with-llvmgccdir=YOUR/PATH doesn't work, instead you are supposed to use --with-llvmgcc=PATH/TO/llvm-gcc and --with-llvmgxx=/PATH/TO/llvm-g++ That will at least get you past my error. Best, Kyle Quoting nicolas geoffray <nicolas.geoffray at gmail.com>: > I am

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,

Hi, I have a problem with compiling the new revision, the file Sifsegv_gc makes a call to the file Sigsegv.cpp but returns as file already allocated: ... llvm [3]: Compiling for Debug + Asserts Sigsegv.cpp build (bytecode) llvm [3]: Compiling Sigsegv.ll to Sigsegv.bc for Debug + Asserts build ( bytecode) llvm [3]: Compiling Sigsegv.bc to Sigsegv.s for Debug + Asserts build llvm [3]: Compiling for

Hello, I've been able to get J3 working with the single and multimap garbage collectors but have hit several snags with Boehm and MMTk. For MMTk I get here: Buildfile: /cs/student/kyleklein/vmkit/mmtk/java/build.xml main: [mkdir] Created dir: /cs/student/kyleklein/vmkit/mmtk/java/classes [javac] Compiling 373 source files to /cs/student/kyleklein/vmkit/mmtk/java/classes

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.

Resending, now that I've signed up to the dev list correctly... Sorry about duplicates. ---------- Forwarded message ---------- From: Zoe Wolk <zoewolk at gmail.com> Date: Mon, Jun 28, 2010 at 3:54 PM Subject: vmkit and llvm 2.8 To: llvmdev at cs.uiuc.edu 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

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

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

I'm trying to compile and link an x86 assembly file with OpenMP calls using llvm-gcc 4.2.1 and I get the following errors: /afs/ cs.wisc.edu/p/vertical/tools/llvm-gcc-4.2/bin/../lib/gcc/i686-pc-linux-gnu/4.2.1/../../../libgomp.a(team.o): In function `gomp_team_start': (.text+0x15a): undefined reference to `__sync_bool_compare_and_swap_4' /afs/

Hi, I am working on compiling vmkit but have run into an error which seems like something that maybe the llvm community would have a better idea of how to solve than vmkit's. The issue is when vmkit is built to compile the MMTk garbage collector it must use the llvm-gcc compiler, at which point MODULE_NAME is defined instead of LIBRARYNAME. This results in the following error

Keith Roberts, Thank you for your suggestion about doing a grep of the source code. We found mmap.S in ../sysdeps/unix/sysv/linux/i386. We looked in mmap.S and found a lot of assembly code. Could you please tell us if any of the assembly code call the kernel syscall handler for mmap.s? Also, we ran make for the kernel Makefile and we obtained the following result shown below. Could you please