GCJ program hanging in __pthread_sigsuspend on exit()

Andrew Haley aph@redhat.com
Tue Dec 6 14:43:00 GMT 2005


Thomas Aeby writes:
 > On Tue, 2005年12月06日 at 11:43 +0000, Andrew Haley wrote:
 > > Looks like some thread is holding the unwinder lock.
 > 
 > Which is a bit surprising since the thread in question is
 > the only one left. All others have gone, maybe one failing to
 > give up the lock before quitting or just failing to signal?
Or the lock itself is corrupt. Hard to say.
 > > It sems very odd to me that you're still using linuxthreads. Do you
 > > need linuxthreads for some special reason?
 > 
 > Ah, that sounds enlightening - in other words I completely missed a
 > point, here. I admit, I have built GCC as well as my java programs
 > using default options, am using glibc 2.3.2 as it was supplied with
 > my Debian/sarge system and am completely unaware of a better
 > alternative to linuxthreads. Ok, I'll do some reading on how to
 > avoid linuxthreads, then (is NPTL the alternative?). I'm feeling a
 > little silly, now :-)
NPTL is generally better than linuxthreads, but which is best for you
depends on your OS. I don't know about Debian Sarge.
If NPTL were available, the first thing I would do is try it.
Andrew.


More information about the Java mailing list

AltStyle によって変換されたページ (->オリジナル) /