Invocation API changes printf/scanf behaviour

1999-03-04 Thread Markus Enzenberger
Hello, I found out that using the Invocation API changes the behaviour of printf/scanf (output of floating point numbers) See the small test program appended. Can someone explain why this happens? I remember that one had to set an environment variable (LOCALE or something similar) on Solaris to

Re: has anyone got the native threads jdk1.1.7a1 running?

1999-03-03 Thread Markus Enzenberger
> I was having this problem but one of the nice folks from the blackdown > porting team told me how to fix it. The fix was to add the libjava.so > file to the process space with this command. > > setenv LD_PRELOAD libjava.so Thanks for the hint. I read something similar in the FAQ but it was me

Re: has anyone got the native threads jdk1.1.7a1 running?

1999-03-01 Thread Markus Enzenberger
Hi, I have a similar problem here. I use the Invocation API with native threads, definitely call JNI_CreateJavaVM with a correct classpath, but JNI_CreateJavaVM hangs for about 30 sec, before it stops with: Can't find class java.lang.System Difficult to say more, it happens only with my larg