X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <48F557D2.9030201@bmts.com> Date: Tue, 14 Oct 2008 22:39:14 -0400 From: Ralph Hempel User-Agent: Thunderbird 2.0.0.6 (X11/20071022) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Strange crash for application linked to cygwin libraries. References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-brucetelecom.com-MailScanner-Information: Please contact Bruce Telecom 519.368.2000 for more information X-brucetelecom.com-MailScanner: Found to be clean X-brucetelecom.com-MailScanner-From: rhempel AT bmts DOT com X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Peter Ross wrote: > On Wed, Oct 15, 2008 at 12:18 PM, Mark Geisert wrote: >> Peter Ross writes: >>> I've written an application which does some initialization and then >>> does a tcp accept. 5 minutes and 20 seconds give or take after doing >>> the tcp.accept the application aborts with exit code 0. If I >>> continually send tcp data to this application then the crash doesn't >>> occur, it is only after 5 minutes and 20 seconds of waiting for I/O. 5 minutes and 20 seconds is 320 seconds which is 32000 milliseconds. It's probably not related, but the maximum signed 16 bit value is 32768. I'm always suspicious when the time is repeatable and the value is some multiple of a power of 2 :-) Ralph -- 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/