Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <02a501c3925b$d837a330$cd8a9dc0@uk.aonix.com> From: "Cliff Hones" To: References: Subject: Re: cygpath hangings Date: Tue, 14 Oct 2003 15:02:45 +0100 Organization: Aonix Europe MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 I'm surprised that this problem seems so intractable. While careful debugging and analysis ought to get to the root of the problem eventually, there is clearly some difficulty in getting a suitable debug session without upsetting what is being examined. [Heisenberg at work.] So alternate approaches could be worthwhile. We seem to be looking for a subtle difference in the environment between a hanging postinstall script (which happens on some systems only, and also only when setup is executed from an explorer window) and a working one. Is it possible cygcheck might show such a difference, or is there another utility which could show system info (such as some of the current internal state of the cygwin shared memory)? Running cygcheck -vs (and/or some other such utility) from a hanging and non-hanging postinstall shell might come up with something. -- Cliff -- 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/