Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com X-Authentication-Warning: hp2.xraylith.wisc.edu: khan owned process doing -bs Date: Wed, 12 Jan 2000 12:36:12 -0600 (CST) From: Mumit Khan To: "Dr. Schroeder, Klaus" cc: cygwin AT sourceware DOT cygnus DOT com Subject: Re: Problem with Java and stdout in newest snapshot In-Reply-To: <387C50EC.6907003@repas-aeg.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 12 Jan 2000, Dr. Schroeder, Klaus wrote: > Using the newest snapshot cygwin1-20000108.dll in my Java JNI > application solved my problem with segmentation faults in function > ioctl. > > But now I'm running into a new problem:As soon, as the jni-dll is loaded > from my Java-Program, the Java standard output (System.out.println) does > no longer work. This bug does not appear with the originalB20.1 > cygwin.dll. This is a "tty" issue as far as I can tell. There may be two ways to solve or work around it: - set CYGWIN=notty before starting the shell where you start Java from. - start it from a windows command shell Does that make the stdout/err show up? Note that if you write to stdout or stderr from the JNI itself, it should show up fine (as well be able to read from it starting from either the snapshot you have or the one just after that). I'll try it out this evening and see if I can understand what's going on. Regards, Mumit -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com