This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: How threads becomes zombie-processes

From: Martin Egholm Nielsen <martin at egholm-nielsen dot dk>
To: java at gcc dot gnu dot org
Date: Tue, 26 Apr 2005 20:09:25 +0200
Subject: Re: How threads becomes zombie-processes
References: <d4l4v2$ile$1@sea.gmane.org> <1114527296.27918.187.camel@localhost.localdomain>

Hi Mark,

Hence my question: Is there a way a thread in gcj can become a zombie thread? E.g. by stop()'ing (deprecated), or similar? If so I would know what to look after in Jessie... I'm running GCJ 3.4.3...
Try using 4.0.0. Process launching and reaping has been almost
completely rewritten.

If you look for a quick solution try running with one of these system
property set to false:
gnu.gcj.runtime.NameFinder.use_addr2line
gnu.gcj.runtime.NameFinder.demangle

Heh! I verified that it works with these properties set to false, the second I received this email :-) Andrew guided me in that direction, after I started guessing about the problem stemming from stacktraces.

So, to both of you, Mark and Andrew, thanks a ton!

BR,
 Martin Egholm

References:
- How threads becomes zombie-processes
  - From: Martin Egholm Nielsen
- Re: How threads becomes zombie-processes
  - From: Mark Wielaard

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]