This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: libgfortran3 respin : status and problem

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 )
> 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:

    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 Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]