public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Max Bowsher" <maxb@ukf.net>
To: <luke.kendall@cisra.canon.com.au>, <cygwin@cygwin.com>
Subject: Re: Problem with setup
Date: Wed, 17 Nov 2004 14:40:00 -0000	[thread overview]
Message-ID: <023f01c4ccb3$5d86bca0$e6ec6f83@robinson.cam.ac.uk> (raw)
In-Reply-To: <20041117013157.0D785837CA@pessard.research.canon.com.au>

luke.kendall@cisra.canon.com.au wrote:
> On 11 Nov, Bobby McNulty wrote:
>>  Guys, theres a major problem with setup.
>>  According to the error I just got, setup is not
>>  closing any of its files after writing them.
>>  I finally got past xorg, and got up to update_info.
>>  I'll rerun setup to get a cygcheck.
>
> I can confirm this.  We took a snapshot of October 26th
> (setup-timestamp: 1098732614), and in that version of setup,

That number you quoted identifies the version of the setup.ini datafile, not 
the setup.exe program.

> none of
> the file handles for any of the temp files of the form (where c:\temp
> is your temporary package directory) c:\temp\http%.....\package.tar.bz2
> is ever released.  The system starts page faulting and the number of
> handles just grows and grows, and eventually setup dies like this:
>
> Microsoft Visual C++ Runtime Error
> Runtime Error!
> Program \\samba\install\win32\cygwin\setup.exe
> This application has requested the Runtime to terminate it in an
> unusual way.  Please contact the application's support team for
> more information.


That's nasty. I wonder why we haven't seen more reports of this.

Is there any reason why your machine should be more susceptible to this? 
(Low memory, any kind of resource limits?)

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/

  parent reply	other threads:[~2004-11-17 14:40 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-11 23:28 Bobby McNulty
2004-11-12  3:41 ` Christopher Faylor
2004-11-12  4:50   ` Bobby McNulty
2004-11-17  1:32 ` luke.kendall
2004-11-17  3:12   ` Luke Kendall
2004-11-17  3:17     ` Bobby McNulty
2004-11-17  6:54       ` Luke Kendall
2004-11-17 17:27         ` Bobby McNulty
2004-11-17 16:00     ` Max Bowsher
2004-11-17  3:17   ` Luke Kendall
2004-11-17 14:40     ` Max Bowsher
2004-11-18  0:10       ` Luke Kendall
2004-11-18  0:19         ` Christopher Faylor
2004-11-18  0:27           ` Bobby McNulty
2004-11-18  0:27         ` Brian Dessent
2004-11-17 14:40   ` Max Bowsher [this message]
2004-11-17 17:41     ` Bobby McNulty
  -- strict thread matches above, loose matches on Subject: below --
2008-02-06 16:35 problem " Igor Peshansky
2008-02-06  1:24 Amadeus W.M.
2008-02-06  2:00 ` Warren Young
2008-02-06  3:30   ` Larry Hall (Cygwin)
2008-02-06  3:57     ` Amadeus W.M.
2008-02-06  4:09       ` Larry Hall (Cygwin)
2008-02-06  7:13         ` Morgan gangwere
2008-02-06  9:46           ` Pedro Macanás
2008-02-06  3:43   ` Amadeus W.M.
2002-05-27 19:26 Problem " Underwood, Jonathan
2002-05-27  6:25 Ton van Overbeek
2002-05-27  3:28 Underwood, Jonathan
2002-05-27  3:33 ` Nicholas Wourms
2002-05-27  3:22 Underwood, Jonathan
2002-05-27  2:14 Robert Collins
2002-05-27  2:05 Underwood, Jonathan
2002-05-12  7:36 Robert Collins
2002-05-12  2:56 Dimitris Zygiridis
2001-09-28  9:41 problem " Eduardo R Larranaga

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='023f01c4ccb3$5d86bca0$e6ec6f83@robinson.cam.ac.uk' \
    --to=maxb@ukf.net \
    --cc=cygwin@cygwin.com \
    --cc=luke.kendall@cisra.canon.com.au \
    /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).