Re: gcj problem with -static option

[FERANDELLE Pascal <pascal dot ferandelle at fr dot thalesgroup dot com>]

> Your best option is to try a more recent gcj release.  4.1 would be a
> good idea.
>

I rebuild everything with GCC 4.1.0 version on PC running RedHat EL 3.0.
My simple HelloWorld program is still "segfaulting" when compiled with the -static option.
But the trace under gdb has changed; I have now :

Program received signal SIGSEGV, Segmentation fault.
0x00000000 in ?? ()
(gdb) info stack
#0  0x00000000 in ?? ()
#1  0x081d0d8e in pthread_create (new_thread=0x869335c, attr=0xbfffa824,
    start_routine=0x8077f40 <really_start>, arg=0x68ff8)
    at ../.././boehm-gc/pthread_support.c:1289
#2  0x08077e37 in _Jv_ThreadStart (thread=0x4cb18, data=0x8693358,
    meth=0x8074c80 <_Jv_ThreadRun(java::lang::Thread*)>)
    at ../.././libjava/posix-threads.cc:488
#3  0x08074672 in java::lang::Thread::start (this=0x4cb18)
    at ../.././libjava/java/lang/natThread.cc:328
#4  0x08049f3d in _Jv_CreateJavaVM (vm_args=0x0)
    at ../.././libjava/prims.cc:1334
#5  0x0804a522 in _Jv_RunMain (vm_args=0x0, klass=0x84b0000, name=0x0, argc=1,
    argv=0xbfffaba4, is_jar=false) at ../.././libjava/prims.cc:1355
#6  0x0804a6b8 in _Jv_RunMain (klass=0x84b0000, name=0x0, argc=1,
    argv=0xbfffaba4, is_jar=false) at ../.././libjava/prims.cc:1401
#7  0x0804a6eb in JvRunMain (klass=0x84b0000, argc=1, argv=0xbfffaba4)
    at ../.././libjava/prims.cc:1407
#8  0x0804822c in main (argc=Cannot access memory at address 0x1
) at /tmp/ccIK0D8H.i:11

Is there any relation between thread creation and "-static" option ?