Re: setup.exe local install with 2.218.2.4 fails, 2.78.2.15 works

[Alan Dobkin <Alan at ADobkin dot Net>]

This new version (2.218.2.6) is the first release of setup.exe 
since the MD5 snapshots that doesn't suck up CPU and memory on 
W2K when installing from a local directory.  Unfortunately, it 
still doesn't work thouugh.  Now the window/process immediately 
disappears when it gets to the progress panel.  No logs are 
written.  If I run it with GDB, I get:

(gdb) run
Starting program: /cygdrive/C/Download/Cygwin/setupnew.exe
warning: LOG: 2 2002/05/14 01:25:31 Starting cygwin install, version
2.218.2.6
warning: LOG: 2 2002/05/14 01:25:31 Current Directory: c:\Download\Cygwin
warning: LOG: 2 2002/05/14 01:25:37 source: from cwd
warning: LOG: 2 2002/05/14 01:25:39 root: D:/cygwin binary system
warning: LOG: 2 2002/05/14 01:25:42 Selected local directory:
P:\Software\Windows\Cygwin
warning: LOG: 1 Found ini file - file://P:\Software\Windows\Cygwin/setup.ini

Program received signal SIGSEGV, Segmentation fault.
[Switching to thread 4124.0xf60]
0x6108d5f8 in ?? ()
(gdb) 

It seems that all of these bug reports are on Win2K and XP Pro.  
Has anyone successfully tested the recent setup.exe releases 
(since the MD5 updates) on either of these platforms?

Alan

--On Tuesday, May 14, 2002 1:13 AM -0400 Christopher Faylor
<cgf-cygwin@cygwin.com> wrote:

> On Mon, May 13, 2002 at 11:58:35PM -0500, A Kerr wrote:
>> With the current setup.exe 2.218.2.4 I successfully downloaded to my 
>> local directory all Cygwin packages from ftp.nas.nasa.gov.  However 
>> when installing from my local download directory, this version of 
>> setup.exe "caused a stack fault in module MSVCRT.dll at 0177:78010618".
> 
> I just uploaded a new version of setup.exe to sources.redhat.com 
> a few minutes ago.  It should work better.
> 
> cgf

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