Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Mail-Followup-To: cygwin-apps AT cygwin DOT com
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
Subject: RE: Setup 2.218.2.4
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Date: Mon, 13 May 2002 18:51:54 +1000
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
Message-ID: <FC169E059D1A0442A04C40F86D9BA7600C607D@itdomain003.itdomain.net.au>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: "Charles Wilson" <cwilson AT ece DOT gatech DOT edu>
Cc: <cygwin-apps AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g4D8q4H18944



> -----Original Message-----
> From: Charles Wilson [mailto:cwilson AT ece DOT gatech DOT edu] 
> Sent: Monday, May 13, 2002 9:59 AM
> Cc: cygwin-apps AT cygwin DOT com
> Subject: Setup 2.218.2.4
> 
> 
> ...seems to have problems.  Can we please revert to 2.194.2.26 as the 
> "production" version, until this problem with the 218 branch 
> is corrected?
> 
> When processing the setup.ini file from a "local" directory 
> (actually on 
> a remote SMB share), it either
> 
> a) fails with a popup that says "setup.exe has generated 
> errors and will 
> be closed by Windows.  You will need to restart the program.  
> An error 
> log is being created."  (However, I can't seem to find this 
> error log...)

Please run it under DebugView/gdb/Visual debugger and see where the
segfault is occuring.

 
> or
> 
> b) consumes memory without bound until it dies with no error 
> message.  I 
> never get to see the chooser.

Great, we have someone who's seen setup's innards able to reproduce
this. I was using a SMB share earlier today, no errors other than two
bluescreens (youch, something dodgy with that kernel :}).

And no, we can't go back, unless someone (not me) wants to build a 2.194
that won't crash with a yacc stack exhaustion.

Rob