search for: j3virtualtablelookup

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 lookup."' failed. 0 vmjc 0x0904fc0a 1 vmjc 0x0904f997 2 0xb77ac400 __kernel_sigreturn + 0 3 libc.so.6...

...t; 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 >> lookup."' failed. >> 0 vmjc 0x0904fc0a >> 1 vmjc 0x0904f997 >> 2...

...at gmail.com> wrote: > 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 > lookup."' failed. > 0 vmjc 0x0904fc0a > 1 vmjc 0x0904f997 > 2 0xb77ac400 __kernel...

...id 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 >>> lookup."' failed. >>> 0 vmjc 0x0904fc0a >>> 1 vmjc 0x0904f997 &gt...

I just noticed there was some .h move around in llvm and fixed the includes in vmkit. Maybe you were just removing the failing includes? In any case, I have updated vmkit for llvm trunk. Let me know if updating helps. Nicolas On Fri, Aug 26, 2011 at 12:00 PM, Akshat Gupta <g.akshat at gmail.com> wrote: > Yep, I am compiling with llvm-gcc. Also I removed the LD flag on the >

Yep, I am compiling with llvm-gcc. Also I removed the LD flag on the configure, it still gives the same segafault. Thanks, Akshat On Fri, Aug 26, 2011 at 4:21 AM, Nicolas Geoffray < nicolas.geoffray at gmail.com> wrote: > On Fri, Aug 26, 2011 at 1:08 AM, Akshat Gupta <g.akshat at gmail.com> wrote: > >> Hi, >> >> Here are my build details. >> OS: >>