[vmkit-commits] About j3-64bit crush

[nicolas geoffray]

That's great news also (the printing of Hello World!).

Congrats! :)

On Mon, Jul 19, 2010 at 7:15 PM, Minas Abrahamyan <minas.subs at gmail.com>wrote:

> 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
>
> _______________________________________________
> 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/20100719/756b19e8/attachment.html>