This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
RE: Deadlock in Class::forName on OSX
- From: "Boehm, Hans" <hans dot boehm at hp dot com>
- To: "Sandro Tolaini" <tolaini at libero dot it>, "Juerg Lehni" <lehni at gmx dot net>
- Cc: <java at gcc dot gnu dot org>
- Date: Wed, 24 May 2006 13:15:06 -0700
- Subject: RE: Deadlock in Class::forName on OSX
It sounds to me like the only hope here might be to get the more
standard pthread-call and signal based thread suspension code working on
MacOS X. I think that was impossible for older versions. A Mac expert
might know whether it's possible for 10.4. Of course, that might well
run into other issues, since it exercises a lot more pthread corner
cases than I would like.
I'm not volunteering. But I wouldn't be unhappy if the nonstandard
thread suspension code disappeared in the long run. (In the short run,
older MacOS X versions will still be around, I expect, so it can't.)
Hans
> -----Original Message-----
> From: java-owner@gcc.gnu.org [mailto:java-owner@gcc.gnu.org]
> On Behalf Of Sandro Tolaini
> Sent: Wednesday, May 24, 2006 11:45 AM
> To: Juerg Lehni
> Cc: java@gcc.gnu.org
> Subject: Re: Deadlock in Class::forName on OSX
>
>
> On 24/mag/2006, at 10:14, Juerg Lehni wrote:
>
> > Would it theoretically be possible to make it compatible
> with Rosetta
> > by changing that part of the code?
>
> No, as far as I know, because this call is needed to get
> informations about thread stack status. Rosetta is probably
> fiddling with the internal thread status frame, hence it will
> not allow you to get it.
> And GC will not work without this informations.
>
> Cheers,
> Sandro
>
>