X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Sat, 26 Mar 2011 10:45:51 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: libgfortran3 respin : status and problem
Message-ID: <20110326094551.GF24762@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <AANLkTikw5F9-M=4Cw9HuGBFUoF2uYUWyOgeosD5STUSw AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <AANLkTikw5F9-M=4Cw9HuGBFUoF2uYUWyOgeosD5STUSw@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

On Mar 26 06:56, marco atzeri wrote:
> Hi,
> I rebuilt lapack, qrupdate, octave and netcdf with the libgfortran3-4.3.4-4.
> 
> ( If you wan to try them, install with
> setup.exe -X  -O -s http://matzeri.altervista.org )
> 
> lapack tests passed
> netcdf also (i am not 100% sure)
> 
> but testing qrupdate I catched another problem.
> The test programs go in a never ending loop:
> 
>  37   15579 [main] tch1dn_sym 4300 fhandler_tty_slave::write: (746):
> tty output_mutex: waiting -1 ms
>  31   15610 [main] tch1dn_sym 4300 fhandler_tty_slave::write: (746):
> tty output_mutex: acquired
>  33   15643 [main] tch1dn_sym 4300 fhandler_tty_slave::write: (789):
> tty output_mutex released

That's not an endless loop as far as Cygwin is concerned.  When a
process writes to the console, then every write is atomic.  To accomplish
that, a mutex is used, like this:

  write()
  {
    acquire mutex
    while (there's still something to write)
      write it
    release mutex
  }

So, what you see is a supposedly endless stream of calls to the write
function.  Usually, if an error occurs, you would also see an error
message.  The only reason you don't see it is if an error already
occured in an earlier call to write.  The important would be prior to
the endless loop then.  Maybe the testcase doesn't check for errors?


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple