This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: GCJ built multithreaded program keeps creating zombies
- From: Thomas Aeby <aeby at graeff dot com>
- To: Wolfgang Bangerth <bangerth at ticam dot utexas dot edu>
- Cc: gcc-bugs at gcc dot gnu dot org, tromey at gcc dot gnu dot org, gcc-gnats at gcc dot gnu dot org
- Date: 19 Dec 2002 00:31:17 +0100
- Subject: Re: GCJ built multithreaded program keeps creating zombies
- References: <Pine.LNX.4.44.0212181716310.15269-100000@gandalf.ticam.utexas.edu>
On Thu, 2002-12-19 at 00:22, Wolfgang Bangerth wrote:
> It can be called a feature: On Linux threads are created basically by
> calling fork/clone. When a process (and thus, here, also a thread) ends,
> it remains a zombie until its return valued is reaped by a waitpid call,
> which should also be what pthread_join does. So unless a thread is joined,
> it will remain a zombie.
Sorry for not having updated the information in my bug report ...
In the meantime I have found out that some nice little daemon installed
on my machines did fill up the realtime signal queue. Since this is a
global queue and no one ever cleans it up if a process decides to leave
signals in it it eventually reached its maximum size and from this time
on realtime signalling stopped working. No need to mention that the
Linux thread implementation uses rt_sigs - which lead to the symptoms
described in my "bug" report. So, this is definitely not to blame on
GCJ - which proved to be a very powerful tool after this silly problem
was fixed!
Best regards,
Tom
----------------------------------------------------------------------------
Thomas Aeby, Kirchweg 40, 1735 Giffers, Switzerland, Voice : (+41)26
4180040
Internet: aeby@graeff.com PGP public key
available
----------------------------------------------------------------------------
A language that doesn't have everything is actually easier to program
in than some that do.
-- Dennis M. Ritchie