David Sayada writes:
> I have been to catch the place where the SIGSEGV occurs, I hope this stack
> trace will help you:
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x0004a284 in TCPServer.HMCServer.selectEventLoop() () at
> TCPServer/HMCServer.java:1849
> 1849 int nReadBytes =
> client.read(info.m_readBuff);
Interesting. A SEGV should not be possible in compiled Java code on
ARM. I'm wondering if this might be a broken gcj installation.
Try
gcj -v
Then look at the line that begins
Reading specs from ...
Send a copy of that file to the list. It should look something like
#
# This spec file is read by gcj when linking.
# It is used to specify the standard libraries we need in order
# to link with libgcj.
#
%rename startfile startfileorig
*startfile: %(startfileorig)
%rename lib liborig
*lib: %{static-libgcj:-non_shared} %{s-bc-abi:-lgcj_bc;:-lgcj}
%{static-libgcj:-call_shared} -lm -lpthread -lrt -lz -ldl %(libgcc)
-lstdc++ %(liborig)
*jc1: -fuse-divide-subroutine -fcheck-references -fuse-boehm-gc
-fkeep-inline-functions
Andrew.
