X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Message-ID:	<d9da72020810141611k334a0b1ds50acbef8183e00dc@mail.gmail.com>
Date:	Wed, 15 Oct 2008 10:11:37 +1100
From:	"Peter Ross" <pro AT missioncriticalit DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Strange crash for application linked to cygwin libraries.
MIME-Version:	1.0
X-Google-Sender-Auth:	e9f30d5f6ec249d6
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

Hi,

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.

I compiled the application with -g and then ran it under gdb, and the
crash doesn't occur then.

Since my application is single threaded and waiting inside tcp accept,
I'm guessing that the problem must be something to do with cygwin
itself.  Maybe something to do with signal handling, but would
appreciate some hints on how I could go about debugging the problem.

Here is the complete list of libraries that I use  -lodbc32 -lole32
-lraptor -lxslt -lcurl -lz -lxml2 -ldb -lssl -lcrypto -lexpat
-lwsock32

Regards,
Peter

--
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/

- Raw text -