Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-Id: <4.3.1.2.20001212102224.02453b30@pop.ma.ultranet.com>
X-Sender: lhall AT pop DOT ma DOT ultranet DOT com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Tue, 12 Dec 2000 10:25:54 -0500
To: "Dunn-Roberts, Richard" <RICHARD DOT R DOT DUNN-ROBERTS AT saic DOT com>,
        cygwin AT sourceware DOT cygnus DOT com
From: "Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
Subject: Re: Std out problems with cygwin1.dll v 1.1.6 and JDK1.3 JNI
In-Reply-To: <979C8411AD31D411986E0008C7CF314301A2B27B@US-Orlando.mail.s
 aic.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 09:37 AM 12/12/2000, Dunn-Roberts, Richard wrote:
>I am the inheritor of a cygwin DLL that works with Java/JNI compiled under
>JDK1.2.2 and cygwin B20.1.  It is being used in a project that is being
>developed under JDK 1.3.
>
>If the DLL is not recompiled, and the java code is recompiled with the
>JDK1.3 compiler, the following error results, and is reported in the command
>window:
>
># An EXCEPTION_STACK_OVERFLOW exception has been detected in native code
>outside the VM.
>
>If the DLL is recompiled with the current net release of cygwin, with
>cygwin1.dll v.1.1.6, the error does not occur, but no output is produced by
>System.out.println().
>
>On Jan 12, 2000, Mumit Khan wrote, in this list:
> > 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 have tried this solution, and it does not seem to work.  Does anyone have
>any suggestions?



No, nothing beyond a clarification.  Set CYGWIN=notty (or make sure CYGWIN
does not contain "tty"), exit any and all apps using Cygwin (including
services, etc), and try again.  The tty setting of Cygwin is only checked 
on DLL load time so if the DLL is already loaded when you make this change,
you won't see any effect.



Larry Hall                              lhall AT rfk DOT com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com