Mail Archives: cygwin/2003/04/26/17:32:53
Phil Bewig wrote:
> Setup version 2.340.2.5, downloaded earlier today.
>
> On one occasion I left it hanging for several hours. For a while
> it would still respond to system messages, for instance I could
> drag the title bar to move the window to a different part of the
> screen. Then it stopped doing even that, and the task window
> sait "not responding." I was previously aware of the "long
> minute" thread, having searched the mailing list, but not of the
> "rush job" thread.
>
> Since posting I have made another attempt, getting farther. I
> was able to select packages on the chooser screen, and
> setup.exe began installing sh.exe. I let it work for over an
> hour, with no other programs running (other than the normal
> background processes). When I came back to my machine,
> setup.exe responded to an attempt to drag the title bar. But
> then I could do nothing else with the machine. Even trying
> to load solitaire gave me the message "insufficient memory;
> try unloading other programs." So obviously something was
> going on with setup.exe consuming memory. There was no
> disk thrashing. I waited another fifteen minutes then killed
> setup.exe.
>
> I assume that what setup.exe is doing at this point is
> extracting sh.exe from the ash-20020731-1.tar.bz2 archive.
> Is that correct? How does the extract process work? What
> program does the extraction? Setup.exe? Or something
> else? And why isn't there a setup log somewhere?
Yes, correct. Setup does the extraction itself - no external programs.
There's no log, because setup buffers the log entries and only writes them
to disc when it exits.
This is a hard problem. I'd be really interested in some of the info you
could get from gdb - but since setup isn't working, you can't install gdb!
Ouch.
Max.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -