Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Date: Tue, 6 Jul 1999 20:06:47 -0400
From: Chris Faylor <cygwin AT sourceware DOT cygnus DOT com>
To: John Wiersba <John DOT Wiersba AT medstat DOT com>
Cc: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: fhandler_base::fork_fixup message
Message-ID: <19990706200647.A1756@cygnus.com>
References: <03F4742D8225D21191EF00805FE62B990205E1A9 AT AA-MSG-01>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
In-Reply-To: <03F4742D8225D21191EF00805FE62B990205E1A9@AA-MSG-01>; from John Wiersba on Tue, Jul 06, 1999 at 06:13:10PM -0400

On Tue, Jul 06, 1999 at 06:13:10PM -0400, John Wiersba wrote:
>I'm still getting messages like:
>
>    0       0 [main] D:\opt\cygwin\bin\bash.exe 1006
>fhandler_base::fork_fixup:
>/jrw/jrw/mdst/sh/tclsh - Win32 error 6, handle 0x1C
>
>even with the 7/5 cygwin1.dll.  Is this being addressed?  I could try to
>help diagnosing this if someone could suggest where to look.  I don't have
>this problem with much older (January) cygwin1.dlls, but all of the recent
>ones I've tried in the past month or so seem to have it.

What, specifically, are you doing?  I see that you're running tclsh but
that's not enough to debug the problem.

You could try using the strace command to track what is going on:

strace -osomefile -f your program arguments here

You'll have to grab the strace program from the cygwin-inst* tar file
on the snapshots page.

cgf

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