JNI calls that don't return

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ian Rogers writes:
 > Andrew Haley wrote:
 > >  > Currently, to the best of my knowledge, classpath's gtk peer code isn't 
 > >  > working with any JVM with M-to-N threading.
 > >
 > > No, that's not true, is it?  Surely it works correctly if blocking
 > > system calls are correctly hooked by the thread library.
 > According to:
 > 
 > http://sourceforge.net/tracker/index.php?func=detail&aid=1147592&group_id=128805&atid=712768
 > (Jikes RVM bug #1147592)
 > 
 > for the only JVM that I know that has M-to-N threading and uses 
 > classpath, this has been broken since 2004-12-20.

Okay, but I cannot see how that is relevant to this particular issue.

 > I was surprised to find this to be the case but if anyone can
 > correct me then I'm happy to be wrong. In any case there are
 > problems to hooking the thread library which prevent it being used
 > as an approach for JVM plugins.

I can't see how that is relevant either.

Maybe you know something I don't.  Is there any wordage in the JNI
spec that forbids blocking calls, or suggests that this might be
problematic?  Is there any wordage in the JNI spec that allows the
Jikes RVM to behave in the way that it does with repect to blocking
calls?

Andrew.



[Index of Archives]     [Linux Kernel]     [Linux Cryptography]     [Fedora]     [Fedora Directory]     [Red Hat Development]

  Powered by Linux