[vmkit-commits] building on Linux x86_64: "Thread 0x110000000 received a SIGSEGV"

[Nicolas Geoffray]

Hi Andrew,

Using GNU Classpath 0.98 is most probably the reason why it crashes. You
should use 0.97.2 instead.

Cheers,
Nicolas


On Mon, Dec 24, 2012 at 10:52 PM, Andrew Purtell <apurtell at apache.org>wrote:

> I've been trying to build vmkit with recent LLVM checked out from SVN.
> (And Classpath 0.98.) The most recent version (of LLVM) I've tried is
> r171041. I've also tried r171201 of LLVM, which looks like it may be pretty
> close to the 3.2 release, with r170964 of vmkit. I've tried building on
> Ubuntu 12.10 and CentOS 6.2.
>
> Googling for "Thread 0x110000000 received a SIGSEGV" turns up an old
> thread from 2011 that claims the x86_64 architecture is not supported by
> vmkit. Is that still true?
>
> I don't mind digging in more but don't really know where to start.
>
> Is there a known good rev of LLVM trunk?
>
> Here's where the build always ends up:
>
> make[2]: Leaving directory `/usr/src/LLVM/vmkit-build/mmtk/mmtk-alloc'
> make[2]: Entering directory `/usr/src/LLVM/vmkit-build/mmtk/java'
> Buildfile: /usr/src/LLVM/vmkit-build/mmtk/java/build.xml
>
> main:
>     [mkdir] Created dir: /usr/src/LLVM/vmkit-build/mmtk/java/classes
>     [javac] /usr/src/LLVM/vmkit-build/mmtk/java/build.xml:4: warning:
> 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set
> to false for repeatable builds
>     [javac] Compiling 380 source files to
> /usr/src/LLVM/vmkit-build/mmtk/java/classes
>     [javac] Note: Some input files use or override a deprecated API.
>     [javac] Note: Recompile with -Xlint:deprecation for details.
>       [jar] Building jar:
> /usr/src/LLVM/vmkit-build/mmtk/java/mmtk-vmkit.jar
>
> BUILD SUCCESSFUL
> Total time: 4 seconds
> llvm[2]: Building Release mmtk-vmkit.jar all
> Thread 0x110000000 received a SIGSEGV: either the VM code or an external
> native method is bogus. Aborting...
> 0  vmjc            0x0000000000ee896f
> 1  vmjc            0x0000000000ee8e19
> 2  libpthread.so.0 0x00002ab388d43cb0
> 3  libc.so.6       0x00002ab389bb6425 gsignal + 53
> 4  libc.so.6       0x00002ab389bb9b8b abort + 379
> 5  vmjc            0x000000000059d4c7 ThrowNullPointerException + 71
> 6  vmjc            0x000000000052ff48
> j3::JavaMethod::invokeIntSpecialAP(j3::Jnjvm*, j3::Class*, j3::JavaObject*,
> __va_list_tag*) + 56
> 7  vmjc            0x00000000005306f5
> j3::JavaMethod::invokeIntSpecial(j3::Jnjvm*, j3::Class*, j3::JavaObject*,
> ...) + 117
> 8  vmjc            0x0000000000543589
> j3::JavaObjectClass::getDeclaredConstructors(j3::JavaObjectClass*, bool) +
> 761
> 9  vmjc            0x000000000054c2d6
> Java_java_lang_VMClass_getDeclaredConstructors + 38
> 10 vmjc            0x00002ab38b810740
> Java_java_lang_VMClass_getDeclaredConstructors + 46950622446736
> Aborted (core dumped)
> make[2]: *** [all] Error 134
> make[2]: Leaving directory `/usr/src/LLVM/vmkit-build/mmtk/java'
> make[1]: *** [all] Error 1
> make[1]: Leaving directory `/usr/src/LLVM/vmkit-build/mmtk'
> make: *** [all] Error 1
>
>
> --
> Best regards,
>
>    - Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>
> _______________________________________________
> vmkit-commits mailing list
> vmkit-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/vmkit-commits
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/vmkit-commits/attachments/20121226/d01f94d9/attachment.html>