Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Info: This message was accepted for relay by smtp03.mrf.mail.rcn.net as the sender used SMTP authentication X-Trace: UmFuZG9tSVZzp26MGqGnOiDOvk+ovHtBf2SLKJ3omWBM3/iHF1a6LM1P7/G9DAfq Message-ID: <3EEE76F2.6050000@cygwin.com> Date: Mon, 16 Jun 2003 22:03:30 -0400 From: Larry Hall Reply-To: cygwin AT cygwin DOT com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030529 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Teun Burgers CC: cygwin AT cygwin DOT com, grahamlamont AT ntlworld DOT com, gnugo-devel AT gnu DOT org, cygwin AT sources DOT redhat DOT com Subject: Re: [gnugo-devel] cgoban + cygwin + w98se References: <3EECC07B DOT 4CA8F70C AT quicknet DOT nl> <3EED1374 DOT 5040004 AT cygwin DOT com> <3EEDF77E DOT 923E9984 AT quicknet DOT nl> In-Reply-To: <3EEDF77E.923E9984@quicknet.nl> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Teun Burgers wrote: > Larry Hall wrote: > > >>Does it work on a recent snapshot ()? > > > No, it doesn't with the 20030608 snapshot. > > fork() is called in a function called stealth(). If from gdb > I step over this function, the Socket operation on non-socket error > is reported. When stepping into this function and then stepping over the > fork() call, the program starts normally with the error. Hm, I guess this is going to take more investigation then. I was hoping it was related to problems recently found in this area but it sounds like it's not. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/