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
content-class:	urn:content-classes:message
MIME-Version:	1.0
X-MimeOLE:	Produced By Microsoft Exchange V6.0.6249.0
Subject:	GDB always receives sigsegv with cygwin 1.3.13-2
Date:	Tue, 15 Oct 2002 19:37:31 -0400
Message-ID:	<83040F98B407E6428FEC18AC720F5D73E5005A@exchange.tropicnetworks.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
From:	"Rolf Campbell" <rcampbell AT tropicnetworks DOT com>
To:	<cygwin AT cygwin DOT com>
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id g9FNbd026909

I tried it with 2 different executables (both C++, both compiled with
GCC3.2).  I tried it with both the stock gdb (20010428-3) & the one
listed as experimental (20020718-1).  I also tried it with both 1.3.13-2
& 1.3.12-4.

The test was, set a breakpoint at the first line of main (done by
default by the gui), and click the run button.  With both programs &
both versions of GDB, the results were the same:  With 1.3.12-4, it
worked fine.  With 1.3.13-2, gdb got the sigsegv signal.

I don't know if this is a problem with gdb, or with cygwin (maybe the
new malloc?).

-Rolf

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