X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org To: cygwin@cygwin.com From: Mark Geisert Subject: Re: Strange crash for application linked to cygwin libraries. Date: Wed, 15 Oct 2008 01:18:17 +0000 (UTC) Lines: 26 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com 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. [...] > Here is the complete list of libraries that I use -lodbc32 -lole32 > -lraptor -lxslt -lcurl -lz -lxml2 -ldb -lssl -lcrypto -lexpat > -lwsock32 You haven't supplied the canonical problem report info as requested in... > Problem reports: ...so only WAGs come to mind: Try it without using wsock32. Cygwin has its own implementation of the TCP/IP networking functions and there might be unpleasant mixing of semantics when wsock32 is explicitly linked in. Something else you could try is running the app under strace to see if anything obviously erroneous sticks out. Most helpful of all for debugging this would probably be a . ..mark -- 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/