This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
RE: Freeze in GC_suspend_handler
- From: "Boehm, Hans" <hans_boehm at hp dot com>
- To: "'Daniel Bonniot'" <Daniel dot Bonniot at inria dot fr>, Andrew Haley <aph at cambridge dot redhat dot com>, java <java at gcc dot gnu dot org>
- Date: Tue, 11 Jun 2002 10:16:31 -0700
- Subject: RE: Freeze in GC_suspend_handler
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. 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.
You may also want to make sure that you have a recent glibc, linuxthreads, and gdb.
Hans
> -----Original Message-----
> From: Daniel Bonniot [mailto:Daniel.Bonniot@inria.fr]
> Sent: Tuesday, June 11, 2002 9:26 AM
> To: Andrew Haley; java
> Subject: Re: Freeze in GC_suspend_handler
>
>
> >
> >
> >What is Thread 2 doing?
> >
> (gdb) thread 2
> [Switching to thread 2 (Thread 2049 (LWP 5490))]#0
> 0x40727b90 in poll ()
> from /lib/libc.so.6
> (gdb) where
> #0 0x40727b90 in poll () from /lib/libc.so.6
> #1 0x4063ed96 in __pthread_manager () from /lib/libpthread.so.0
> #2 0x4063efc0 in pthread_start_thread () from /lib/libpthread.so.0
>
>