Re: yay! was: native threads, SIGSTOP, and Invocation API

1999-09-10 Thread Gene McCulley
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > "Juergen" == Juergen Kreileder <[EMAIL PROTECTED]> writes: > Gene McCulley writes: Gene> Under glibc 2.0 and SMP, the native threads version of Gene> jdk117_v3 is unreliable. Juergen> We are working on it. Cool. Gene> Ano

Re: yay! was: native threads, SIGSTOP, and Invocation API

1999-09-10 Thread Juergen Kreileder
> Gene McCulley writes: Gene> Under glibc 2.0 and SMP, the native threads version of Gene> jdk117_v3 is unreliable. We are working on it. Gene> Another problem with the Invocation API is embedding Java Gene> GUI apps in applications that use X/Motif. I am currently Gene

yay! was: native threads, SIGSTOP, and Invocation API

1999-09-10 Thread Gene McCulley
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I thought that I would follow up on my previous message as I have resolved that problem and wanted to share the solution with the list. It seems that the problem was that I was creating the VM and going into my event loop in my main thread. This see

Re: native threads, SIGSTOP, and Invocation API

1999-09-08 Thread Matt Welsh
I had quite a few problems using native threads with JDK 1.1.7v3. These were never resolved but the Blackdown folks said that the forthcoming 1.1.8 release might fix some of the problems. You should be able to use gdb to find out what's going on; you can tell gdb to report the various signals

native threads, SIGSTOP, and Invocation API

1999-09-08 Thread Gene McCulley
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, I apologize if this hits the list twice. I sent it before I was subscribed and it appears to me that it was silently discarded. This is a verbatim repost except for the information about the kernel version: I am trying to use the jdk117_