gcj on Nexenta OS

[Tom Tromey]

>>>>> "David" == David Daney <ddaney@avtrex.com> writes:

David> You don't say what architecture this is running on .  It would be
David> helpful to know that.  Also it would be nice to have a back trace from
David> the failure point.

David> It looks like you did something similar to making a call through a
David> NULL function pointer.

David> I don't want to sound discouraging, but I don't think much libgcj
David> porting work has been done for Nexenta.  So if you want to get it
David> working, you may be spending a lot of quality time with gdb.  Also I
David> would not rule out problems with the C library or linker as causes.
David> But really from the information you gave it is very difficult to say
David> what is wrong.

In addition to all this, perhaps the machinery to turn a SEGV into an
exception doesn't work on this platform (yet).  You could test that by
building libgcj with explicit NULL pointer checks, and see if that
helps.  Also note that the GC may intentionally provoke a SEGV at
startup, though based on the "??" I would guess that this is not what
you are seeing in this case.

The wiki page on debugging libgcj may be of some interest.

Another thing worth doing before getting too heavily into debugging
libgcj is to make sure that the GC is working.  "make check" in the GC
build directory ought to do it.

Tom