similar to: [LLVMdev] Unable to run a java class by j3

Displaying 20 results from an estimated 100 matches similar to: "[LLVMdev] Unable to run a java class by j3"

2011 Jul 19
0
[LLVMdev] Unable to run a java class by j3
Hi Sarah, You should use classpath 0.97.2 and not 0.98 (isn't the error message obvious? :-)). So please try with classpath 0.97.2, and let me know if it works. Nicolas On Tue, Jul 19, 2011 at 3:44 PM, Sarah <sarah.berenji at gmail.com> wrote: > Hey all, > I installed vmkit-0.29 following instructions at > http://vmkit.llvm.org/get_started.html > I attempt to run a simple
2011 Aug 24
0
[LLVMdev] VMKit build error
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)
2011 Aug 23
2
[LLVMdev] VMKit build error
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
2012 Dec 01
0
[LLVMdev] Problem executing Swing application with j3
Hi all, I have a question about vmkit and especially j3 VM. I compiled and installed it without any problems. But I have this error as soon as I try to launch a Swing application (Swing HelloWorld) : j3: ctthread.cpp :71 : void vmkit::Thread::endKnownFrame(): Assertion failed. « lastKnownFrame->currentIP == 0 » What I'm doing wrong ? Thanks in advance, Baptiste. -------------- next
2012 Dec 22
0
[LLVMdev] Problem executing Swing application with j3
Hi Baptiste, Just to let you know that I have just fixed the problem. You can now either use trunk or release 0.32 and the program now runs. Cheers, Nicolas On Mon, Dec 3, 2012 at 8:09 PM, Baptiste Saleil <baptiste.saleil at gmail.com>wrote: > Hi Nicolas, thanks for your answer. > > The swing hello world is the following (Running perfectly with OpenJDK) : > > public class
2011 Jul 20
0
[LLVMdev] Unable to run a java class by j3
Did you link the shared libraries? (step 2). Also, can you send me your configure option? Nicolas On Wed, Jul 20, 2011 at 3:45 PM, Sarah <sarah.berenji at gmail.com> wrote: > Nicolas Geoffray <nicolas.geoffray <at> gmail.com> writes: > > > > > > > Hi Sarah, > > > > You should use classpath 0.97.2 and not 0.98 (isn't the error message
2011 Jun 10
0
[LLVMdev] [VMKit] Bug in J3 User.Name detection
Please excuse the previous mail. My mailclient misbehaved. The below code to check for the environment variable NAME and for setting a default username of "" fails, because the else paths are only taken when there inside if condition is false anyways. The elses should not be there but instead each method should be used until a username is returned.
2011 Jul 20
2
[LLVMdev] Unable to run a java class by j3
Nicolas Geoffray <nicolas.geoffray <at> gmail.com> writes: > > > Hi Sarah, > > You should use classpath 0.97.2 and not 0.98 (isn't the error message obvious? ). > So please try with classpath 0.97.2, and let me know if it works. > > _______________________________________________ > LLVM Developers mailing list > LLVMdev <at> cs.uiuc.edu
2011 Jun 10
2
[LLVMdev] [VMKit] Bug in J3 User.Name detection
Hello List, I'm currently trying to compile VMKit for the L4 Operating System and the L4Re Runtime environment for my student project. While doing so I stumbled upon a bug in the implementation of lib/J3/Classpath/ClasspathVMSystemProperties.inc The current version first tries to get the username by checking the LOGNAME environment variable. If this is NULL it then checks tmp =
2011 Jul 24
0
[LLVMdev] Unable to run a java class by j3
Hi Sarah, On Sun, Jul 24, 2011 at 6:28 AM, Sarah <sarah.berenji at gmail.com> wrote: > > I created links in "/usr/local/classpath/lib" where my classpath objects > are > installed. Since it didn't work I tried these paths too: in classpath's > source > "/usr/local/classpath-0.97.2/lib" & also in "/lib"!! The error didn't >
2013 Apr 16
0
[LLVMdev] [vmkit]Problems when modifying J3
Hi Julien, I also tried to add a field and get the same error as you. In theory, to add a field in JavaClass or JavaCommonClass you have to put your field at the end of the declaration list (in order to minimize index changes in J3Intrinsics) in C++ code and in LLVMRuntime/runtime-single.ll We are working on this issue to see what is going wrong. The problem is the fact that the error is not
2013 Apr 17
1
[LLVMdev] [vmkit]Problems when modifying J3
Hi Julien, I found out what was missing for adding a field to JavaClass. While precompiling Java code (JavaAOTCompiler) we create an equivalent LLVM Constant object for each class. So modifying the internal representation of a class means that you also have to modify the AOTCompiler. Here is a patch with a tiny example where an int is added to JavaClass. If you want to add more complex
2013 Apr 15
2
[LLVMdev] [vmkit]Problems when modifying J3
Hi all, I am currently working with vmkit (especially on J3) for a student project, I want to made some experimentations on J3. I see in the file lib/j3/VMCore/JavaClass.h that if I want to add some attributes in the class JavaClass I must change a few thing in LLVMRuntime/* and in JnjvmModule.cpp. But JnjvmModule.cpp does not exist anymore. So my first question is : what is the equivalent of
2011 Jul 24
2
[LLVMdev] Unable to run a java class by j3
Nicolas Geoffray <nicolas.geoffray <at> gmail.com> writes: > > > Did you link the shared libraries? (step 2). > > Also, can you send me your configure option? > > NicolasOn Wed, Jul 20, 2011 at 3:45 PM, Sarah <sarah.berenji <at> gmail.com> wrote: > Nicolas Geoffray <nicolas.geoffray <at> gmail.com> writes: > > > > >
2011 Aug 24
2
[LLVMdev] VMKit build error
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
2013 Sep 12
0
[LLVMdev] VmKit - Error in j3/precompiler after a big surgery to MMTk part
Hi Yi, The precompiler is in charge of translating the most common classes of the Java runtime library to llvm code (typically, java.lang.Object), in order to natively compile these classes and decrease the bootstrap time. So, if you have a segmentation fault at this stage, it means that you have broken something in the interface between MMTk and VMKit. If it can helps you: * during a first
2013 Sep 12
2
[LLVMdev] VmKit - Error in j3/precompiler after a big surgery to MMTk part
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
2010 Jul 13
1
[LLVMdev] VMKit - J3's startup time
Hi all, Just a quick question. Is there any way to reduce the startup time of J3? Thanks, Chanwit
2007 Apr 18
1
[RFC, PATCH 7/24] i386 Vmi memory hole
Create a configurable hole in the linear address space at the top of memory. A more advanced interface is needed to negotiate how much space the hypervisor is allowed to steal, but in the end, it seems most likely that a fixed constant size will be chosen for the compiled kernel, potentially propagated to an information page used by paravirtual initialization to determine interface compatibility.
2007 Apr 18
1
[RFC, PATCH 7/24] i386 Vmi memory hole
Create a configurable hole in the linear address space at the top of memory. A more advanced interface is needed to negotiate how much space the hypervisor is allowed to steal, but in the end, it seems most likely that a fixed constant size will be chosen for the compiled kernel, potentially propagated to an information page used by paravirtual initialization to determine interface compatibility.