no stacktrace available

Tue Dec 14 13:43:00 GMT 2004

oops, i spoke too soon. got a core dump that may again be related to 
threading/gc. i vaguely remember the form of the error - an infinite 
stack trace.
...
#494 0x485f01b0 in GC_clear_stack_inner () from 
/usr/pkg/gcc3/lib/libgcj.so.4
#495 0x485f01b0 in GC_clear_stack_inner () from 
/usr/pkg/gcc3/lib/libgcj.so.4
#496 0x485f01b0 in GC_clear_stack_inner () from 
/usr/pkg/gcc3/lib/libgcj.so.4
#497 0x485f01b0 in GC_clear_stack_inner () from 
/usr/pkg/gcc3/lib/libgcj.so.4
#498 0x485f01b0 in GC_clear_stack_inner () from 
/usr/pkg/gcc3/lib/libgcj.so.4
#499 0x485f01b0 in GC_clear_stack_inner () from 
/usr/pkg/gcc3/lib/libgcj.so.4
#500 0x485f01b0 in GC_clear_stack_inner () from 
/usr/pkg/gcc3/lib/libgcj.so.4
#501 0x485f01b0 in GC_clear_stack_inner () from 
/usr/pkg/gcc3/lib/libgcj.so.4
#502 0x485f01b0 in GC_clear_stack_inner () from 
/usr/pkg/gcc3/lib/libgcj.so.4
#503 0x485f01b0 in GC_clear_stack_inner () from 
/usr/pkg/gcc3/lib/libgcj.so.4
#504 0x485f01b0 in GC_clear_stack_inner () from 
/usr/pkg/gcc3/lib/libgcj.so.4
#505 0x485f01b0 in GC_clear_stack_inner () from 
/usr/pkg/gcc3/lib/libgcj.so.4
Michael Koch wrote:
>Am Dienstag, 14. Dezember 2004 14:34 schrieb Bart Locanthi:
>>>>wups, heh, my bad..
>>>>i'd forgotten about this, but one of the clever things i do in my
>>largish application was to paw through stack trace output at high
>>logging levels to get the procedure:line-no of the calling entity.
>>>>which is highly dependent on the output format of stack traces. i
>>remember doing something 18 months ago to avoid this when i was
>>last trying to port to gcj/netbsd.
>>>>so anyway, i reduced the logging level and the app works fine. woo
>>hoo!!
>>>>i haven't looked at what log4j does here, but i imagine the rhug
>>folk had to hack it in a similar way for it to work under gcj.
>>>>>>Ah, there is a good chance that this is fixed at least in GCJ 4.0 
>then.
>>>Michael
>>