Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: 22 Oct 2001 16:31:36 -0400
Message-ID: <20011022203136.5144.qmail@lizard.curl.com>
From: Jonathan Kamens <jik AT curl DOT com>
To: jik AT curl DOT com
CC: cygwin-developers AT cygwin DOT com
In-reply-to: <20011022193036.3609.qmail@lizard.curl.com> (message from
	Jonathan Kamens on 22 Oct 2001 15:30:36 -0400)
Subject: Re: 1.3.4 status?
References: <3BD4635D DOT 1060208 AT ece DOT gatech DOT edu> <20011022142729 DOT A10309 AT redhat DOT com> <20011022192430 DOT 3581 DOT qmail AT lizard DOT curl DOT com> <20011022193036 DOT 3609 DOT qmail AT lizard DOT curl DOT com>

OK, I get a crash inside the DLL when I try to launch pretty much any
Cygwin executable if I compile the DLL with "CFLAGS='-g -O3'".  The
crash goes away if I use "-g -O2" instead.  I'm having trouble getting
it to crash inside gdb so I don't have a stacktrace yet, but I'll keep
trying.  If somebody else wants to try this and see if it happens for
you, feel free.

Also, the stackdump file seems to be pretty useless, so I suspect that
there may be some memory corruption going on.  I'm probably going to
try enabling malloc debugging to see what happens.

I'm using gcc-2.95.3-5.

  jik