Freeze in GC_suspend_handler

Tue Jun 11 10:30:00 GMT 2002

>>>Thread 3 is waiting for a GC to complete. Check GC_stopping_thread and GC_stopping_pid to see if you can identify which thread initiated the collection. 
>Sorry, I have little experience with gdb. Could you tell me what gdb 
commands will do that?
>If I had to make a wild guess, I'd say that that thread crashed for some reason, and is no longer around. (It's clearly neither thread 3 (which hung) or thread 2, which is the manager thread. You might also look at thread 1.)
>>In my experience, linuxthreads sometimes doesn't seem to notice of one of the threads dies with e.g. a SIGSEGV.
>There has been a SIGV before, indeed (see my previous post -- later than 
the one you were answering).
A question is whether that SEGV is the bug itself, or is a normal 
behaviour of libgcj when looking for a (possibly not exinsting) class by 
reflexion.
>You may also want to make sure that you have a recent glibc, linuxthreads, and gdb.
>I would think so, since I run Debian 3.0 (testing). libc6 is 2.2.5, gdb 
is 5.2.cvs20020401-6. I am not sure how to check linuxthreads version. 
Kernel is 2.4.18.
Daniel