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:	"Gary R Van Sickle" <tiberius AT braemarinc DOT com>
To:	"Cygwin Mailing List \(E-mail\)" <cygwin AT sources DOT redhat DOT com>
Subject:	More on "Signal 11" problem / GCC vs. 1.3.19+
Date:	Mon, 27 Jan 2003 16:16:30 -0600
Message-ID:	<000801c2c651$bf2886b0$2101a8c0@BRAEMARINC.COM>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1106
Importance:	Normal

Haven't found the problem, but I've narrowed it down some, so this is mainly
to see if anybody's memory gets jogged:

I'm gdb'ing "gengtype.exe", the executable that's "Signal 11"ing and killing
the compile of GCC cvs HEAD on cygwin1.dll versions 1.3.19 and later.  It's
SIGSEVing on line 2382 of gengtype.c, a call to "oprintf()".  The actual
SIGSEV comes a few calls down the stack, in (what I believe is) Cygwin's
vasprintf().  It's far from the first call to either oprintf() or
vasprintf(), so I suppose it could be pretty much anything, but if anybody
has any "Oh yeah, I bet that's the change I made to <...>", feel free to
fill in the blank.

--
Gary R. Van Sickle
Braemar Inc.
11481 Rupp Dr.
Burnsville, MN 55337


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