Message-Id:	<200212102116.gBALGwE20584@delorie.com>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
From:	markmadsen1 AT attbi DOT com
To:	cygwin AT cygwin DOT com
Subject:	crashing in select
Date:	Tue, 10 Dec 2002 21:16:30 +0000
X-Authenticated-Sender:	bWFya21hZHNlbjFAYXR0YmkuY29t

I'm using W2K Pro and select ( I think it is there ) is dumping core. The reason
I am not sure is that when I run the app in gdb, the crash is not in the main
thread but the addresses on the stack match those of the main thread after it
calls select. (The app doesn't start any additional threads on its own.)

The conditions under which this occurs is a pretty heavy load of open sockets
(>1000) and all open descriptors are selected.

Any thoughts or comments on this? Unfortunately, I can't get cygwin to generate
a core file in this case either.

-Mark

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -