[vmkit-commits] About j3-64bit crush

Minas Abrahamyan minas.subs at gmail.com
Mon Jul 19 10:15:01 PDT 2010


Wow, Alan!
Thank you very much! You're like a magician, how did you know?

It now works for me:
<<<
[bin]$ ./j3 HW 2>log.txt
Hello, world!
[bin]$
>>>

Last lines of log.txt are:
<<<
compiling java/io/FileOutputStream.write()
--> end compiling java/io/FileOutputStream.write()
;resolve {Class gnu/java/nio/FileChannelImpl
}resolve; //Class gnu/java/nio/FileChannelImpl
compiling gnu/java/nio/FileChannelImpl.write()
--> end compiling gnu/java/nio/FileChannelImpl.write()
compiling gnu/java/nio/VMChannel.write()
--> end compiling gnu/java/nio/VMChannel.write()
native compile gnu/java/nio/VMChannel.write()
--> end native compile gnu/java/nio/VMChannel.write()
--> end native compile gnu/java/nio/VMChannel.write()
Hello, world!
compiling java/io/OutputStream.flush()
--> end compiling java/io/OutputStream.flush()
>>>
//except for "Hello, world!" printed on stdout

I don't know what is right way to transfer classpath build system that
 "no-omit" option, but what I did was
change in ./configure script.

See patch for it I'm attaching; to be applied with:
patch ./configure.orig ./classpath_configure64.patch

-Minas

PS Allan, maybe you're compiling something other than "Hello World" -
then, I hope, next my patch (related with Debug output) will help you.
Thanks again!

PPS
JFYI, article "Getting the call stack without a frame pointer":
http://www.yosefk.com/blog/getting-the-call-stack-without-a-frame-pointer.html

On Mon, Jul 19, 2010 at 6:19 AM, Allan Tong <actong88 at gmail.com> wrote:
> Hi,
>
> I was having the same problem here.  It turns out that the 64-bit
> build of Classpath was omitting frame pointers.  Once I recompiled
> Classpath with -fno-omit-frame-pointer, the StackWalker was able to
> get past the offending stack frame and find the calling Java method.
> This resolves the segfault, though now I get a ClassNotFoundException
> trying to find my main class, which I haven't looked into yet.
>
>  - Allan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: classpath_configure64.patch
Type: text/x-patch
Size: 1264 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/vmkit-commits/attachments/20100719/35754a6f/attachment.bin>


More information about the vmkit-commits mailing list