From: "Max Bowsher" <maxb@ukf.net>
To: <pbewig@swbell.net>, <cygwin@cygwin.com>
Subject: Re: setup.exe: Woe is me!
Date: Sun, 27 Apr 2003 00:47:00 -0000 [thread overview]
Message-ID: <00ae01c30c3b$5dcdad70$78d96f83@pomello> (raw)
In-Reply-To: <01C30C0E.1DF55A40.pbewig@swbell.net>
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/
next prev parent reply other threads:[~2003-04-26 21:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-26 23:45 Phil Bewig
2003-04-27 0:47 ` Max Bowsher [this message]
2003-04-27 0:51 ` Igor Pechtchanski
2003-04-27 2:40 ` Martin Gainty
-- strict thread matches above, loose matches on Subject: below --
2003-04-28 4:48 Phil Bewig
2003-04-27 16:59 Phil Bewig
2003-04-27 16:49 Phil Bewig
2003-04-27 19:17 ` Elfyn McBratney
2003-04-27 9:48 Phil Bewig
2003-04-27 11:25 ` Greg McCrory
2003-04-27 12:14 ` Igor Pechtchanski
2003-04-27 13:10 ` Max Bowsher
2003-04-27 15:30 ` Hannu E K Nevalainen (garbage mail)
2003-04-28 1:09 ` Robert Collins
2003-04-28 8:04 ` Igor Pechtchanski
2003-04-28 13:41 ` Robert Collins
2003-04-27 8:55 Phil Bewig
2003-04-27 8:54 Phil Bewig
2003-04-27 8:51 Phil Bewig
2003-04-27 8:34 Phil Bewig
2003-04-26 21:31 Phil Bewig
2003-04-26 21:58 ` Igor Pechtchanski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='00ae01c30c3b$5dcdad70$78d96f83@pomello' \
--to=maxb@ukf.net \
--cc=cygwin@cygwin.com \
--cc=pbewig@swbell.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).