Re: [rvm-research] Running RVM fails in Mavericks
Erik Österlund <[email protected]>
| Newsgroups | gmane.comp.java.jikes.rvm.devel |
|---|---|
| Message-ID | <[email protected]> |
The problem seems to be before a thread terminates because it seems to instantly die when bootThread() is called. When just running rvm I get the following error message: JikesRVM: TROUBLE. Got a signal (Segmentation fault: 11; #11) from outside the VM's address space in thread 0xa08d81a8. JikesRVM: UNRECOVERABLE trapped signal 11 (Segmentation fault: 11) handler stack 938b44e0 si->si_addr 0x0 cs 0x0000001b ds 0x00000023 es 0x00000023 fs 0x00000000 gs 0x0000000f ss 0x00000023 edi 0x00018f8c esi -- PR/VP 0x00040000 ebp 0x33090054 esp -- SP 0x3308ffec ebx 0x00005858 edx 0x00000000 ecx 0x00000012 eax 0x00000645 eip 0x938b44e0 trapno 0x0000000d err 0x00000000 eflags 0x00010212 fpregs 1 oldmask 0xffffffff cr2 0x00000000 fp0 0x0000000000000000ffff fp1 0x0100000000000000ffff fp2 0x00000000000000000000 fp3 0x0015000000000000ffff fp4 0x9100ffe300000000ffff fp5 0x00000000000000000000 fp6 0x000000000000bb78400b fp7 0x00000000fffeffff401d JikesRVM: internal error invalid native thread address (not an address 40000) Abort trap: 6 I tried to print the ip, tr and sp right before bootThread() is being called and got the following output: Booting thread: [ip:3307726436034664,tr:17004330900fc,sp:200000370] So as we can see, the native thread magically transformed from 17004330900fc before bootTrhead() to 40000 in the signal handler. Am I using the wrong compiler? Am I supposed to use Apple's clang rather than the GNU gcc4.7? Or maybe the asm __x86_64__ asm code needs fixing? Or maybe I'm doing something wrong... Regards, Erik Österlund On 09 Apr 2014, at 19:03, Erik Brangs <[email protected]> wrote: > Hi, > > On 09.04.2014 17:22, Erik Österlund wrote: >> I built JikesRVM from two Mac OS X x86_64 machines with gcc 4.7 and 4.9. They both managed to build the VM without problems, but crash when VM is booting, complaining that the native thread is outside the bounds of the VM memory. >> >> Is this a well known problem? > > This sounds like it could be related to RVM-1027 ( http://jira.codehaus.org/browse/RVM-1027 ) but it's hard to tell without more information. There's a workaround for RVM-1027 in the latest version from the repository. > > > Kind regards, > > Erik Brangs > > ------------------------------------------------------------------------------ > Put Bad Developers to Shame > Dominate Development with Jenkins Continuous Integration > Continuously Automate Build, Test & Deployment > Start a new project now. Try Jenkins in the cloud. > http://p.sf.net/sfu/13600_Cloudbees > _______________________________________________ > Jikesrvm-researchers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/jikesrvm-researchers ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees