Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Thu, 12 Dec 2002 11:57:36 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: pipe improvements in snapshot
Message-ID: <20021212165736.GA14986@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20021211041250 DOT GA31215 AT redhat DOT com> <094401c2a1da$954ab980$1d6cba8c AT sfdev3>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <094401c2a1da$954ab980$1d6cba8c@sfdev3>
User-Agent: Mutt/1.5.1i

On Thu, Dec 12, 2002 at 07:32:16AM -0500, Norman Vine wrote:
>Christopher Faylor writes:
>
>> In the most recent cygwin snapshot (uploading now) I've attempted to
>> work around the 10ms delay in pipe reads.
>
>< snip >
> 
>> Please check out the latest snapshot and report here if there are
>> problems.  I haven't yet tried this on Windows 9x class systems so it's
>> entirely possible that there is a problem there.
>
>With a Cygwin CVS tree I built this AM < (2) below > 
>rxvt has problems when configuring a project from a build directory
>
>ie 
>$TOP_DIR
>     src
>     build
>
>cd $TOP_DIR/build
>../configure
>
>The problems vary from run to run ranging from 'error parsing uname'
>to program hang < recoverable with 'ctrl-C' > making me suspect a
>possible data loss
>
>Using the gcc option -pipe seems to allow the configure process
>Using the -pipe flag I have not seen the uname error but it does
>eventually hang when actually creating the Makefiles
>
>This project uses libtool
>
>With the CVS tree build (1) below I do not experience this
>
>(1) 10-Dec-2002   7:10:38a    6,683,847  cygwin-20021210.tar.gz
>(2) 12-Dec-2002   6:09:42a    6,688,318  cygwin-20021212.tar.gz
>
>The times are EST and the tarballs are created by a script that
>does a CVS update, make, make tarball which takes ~20 minutes
>so the CVS update time should be approximately 20 minutes earlier
>
>Any 'tips' as to how to best debug this appreciated 

- Attach to the hung process with gdb and see where it is hung.

- Provide cygcheck output.

- Run under strace and see if you can infer where hangs or problems
  are occurring.

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/