This is the mail archive of the
mailing list for the Cygwin project.
Re: Standard out writes fail after cygwin generated dll loaded
- From: "José Lorenzo Mon" <lorenzo_mon at hotmail dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 07 Mar 2003 12:18:51 +0100
- Subject: Re: Standard out writes fail after cygwin generated dll loaded
- Reply-to: jose dot mon at teleline dot es
Hi Luis and All,
When trying to run through the JNI native C code compiled in a DLL
using Cygwin, I found that standard Java output stops to work as
soon as the DLL is loaded. However, if the same code is compiled
without Cygwing (-mno-cygwin) the Java output works OK after and
before loading the DLL.
I am having same problem. My tests more in detail:
- When running the Java VM *from a cygwin shell*, the stdout channel
works OK before and after loading the DLL generated with the cygwin
gcc. However, the stderr stops working after loading the DLL.
After loading the DLL and using the stdout and stderr
channels by the native C function, the Java program is only able to use
the stdout channel.
- When running the Java VM *from a windows shell*, both the stdout and
stderr channels stop working after loading the DLL.
- When compiling the dll *without* cygwin support (with the
"-mno-cygwin" flag), both channels work ok in both shells.
- The version employed of "jni.h" does not seem to affect to the
results. I have tried both versions, the one comming with cygwin and
the version provided with the JDK distribution (defining by
- The version of the JDK (1.3 or 1.4) does not seem to affect to the
- I have tried with different combination of flags for the gcc compiler
and they do not seem to affect to the results.
Does anyone know why this is happening or a possible solution?
Thanks in advance,
Help STOP SPAM with the new MSN 8 and get 2 months FREE*
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html