> Andrew Burgess writes:
Andrew> Ack. RTFM! I did read all the READMEs but forgot the FAQ.
>> The green threads libjava.so overrides some system calls (open, close,
>> ...). So you'll have to defer system calls until after the call to
>> JNI_CreateJavaVM.
Andrew> I trie
>Andrew> I've been using the Blackdown JDK sucessfully for many
>Andrew> weeks now. I recently tried to invoke a java vm from an
>Andrew> existing C application using the JNI_CreateJavaVM call. It
>Andrew> seems that simply linking with libjava_g.so (where
>Andrew> JNI_CreateJ
On Sun, 1 Nov 1998 11:12:30 -0800, Andrew Burgess wrote:
>
>Regarding my problem with open(), upon reading further I see in
>tutorial/native1.1/implementing/invo.html:
>
>>The user-level Java programming language thread implementation on Solaris
>>requires the Java Virtual Machine to redirect ce
Regarding my problem with open(), upon reading further I see in
tutorial/native1.1/implementing/invo.html:
>The user-level Java programming language thread implementation on Solaris
>requires the Java Virtual Machine to redirect certain Solaris system calls. The
>set of redirected system calls
> Andrew Burgess writes:
Andrew> I've been using the Blackdown JDK sucessfully for many
Andrew> weeks now. I recently tried to invoke a java vm from an
Andrew> existing C application using the JNI_CreateJavaVM call. It
Andrew> seems that simply linking with libjava_g.so (wher
I've been using the Blackdown JDK sucessfully for many weeks now.
I recently tried to invoke a java vm from an existing C application
using the JNI_CreateJavaVM call. It seems that simply linking
with libjava_g.so (where JNI_CreateJavaVM is defined) breaks calls
to open(). Here is a small example.
