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
Date: Wed, 11 Dec 2002 17:02:30 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: crashing in select
Message-ID: <20021211170230.V7796@cygbert.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <FED2EC3075A99C4CBB8D63AABBC3396E1FAFF2 AT daa21794exc001 DOT divine DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <FED2EC3075A99C4CBB8D63AABBC3396E1FAFF2@daa21794exc001.divine.com>
User-Agent: Mutt/1.3.22.1i

On Wed, Dec 11, 2002 at 08:25:34AM -0600, Madsen, Mark wrote:
> Any thoughts or comments on this? Unfortunately, I can't get cygwin to
> generate
> a core file in this case either.

Two possible ways.

Try debugging using gdb.  Add 'error_start=C:/gdb.cmd' to the env var
$CYGWIN.  C:/gdb.cmd looks like this:

  C:/cygwin/bin/gdb -nw %1 %2

Note that this implies having your own debug build of Cygwin.

Otherwise create a *simple* testcase (in C) which allows to reproduce
the problem easily and send it to this list.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

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