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
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: crashing in select
Date: Wed, 11 Dec 2002 11:21:57 -0600
Message-ID: <FED2EC3075A99C4CBB8D63AABBC3396E0ED440@daa21794exc001.divine.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "Madsen, Mark" <Mark DOT Madsen AT divine DOT com>
To: <cygwin AT cygwin DOT com>
X-OriginalArrivalTime: 11 Dec 2002 17:21:57.0716 (UTC) FILETIME=[CEF4E940:01C2A139]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id gBBHMP513063

I've tried the error_start to create the core and I endup with a
stackdump indicating that the stack was corrupt while trying to dump the
core. I have created the problem while running within GDB. When the
problem occurs there are 4 active threads. The main thread which shows
my trace with symbols up until the call to select and then 4 more levels
after that. The other three thread stack frames are identical and the
same as the frame of the first thread after the call to select. The
error occurs in the 4th thread.

I am attempting to create a simpler version of the source now, but it is
taking time. ;)

-Mark

-----Original Message-----
From: Corinna Vinschen [mailto:corinna-cygwin AT cygwin DOT com] 
Sent: Wednesday, December 11, 2002 10:03 AM
To: cygwin AT cygwin DOT com
Subject: Re: crashing in select

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/


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