On Sat, Mar 26, 2011 at 5:05 PM, Corinna Vinschen wrote: > On Mar 26 11:33, marco atzeri wrote: >> On Sat, Mar 26, 2011 at 10:45 AM, Corinna Vinschen wrote: >> > 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? >> >> the test case is a normal Fortran program that call numerical functions and >> print output with a really standard "write" command, nothing fancy. >> It used to work fine with previous libgfortran3-4.3.4-3 and cygwin-1.7.7 > > What about current libgfortran3 and cygwin 1.7.7? What about previous > libgfortran3 and cygwin 1.7.8?
I will make all the test as soon I built a simpler test case involving only libgfortran3 and cygwin . Currently qrupdate require lapack and lapack 3.2.2-1 was broken by the libgfortran3 update. Today I have cygwin-1.7.7 , libgfortran3-4.3.4-3, lapack-3.2.2-1, qrupdate-qrupdate-1.1.0-1 fine cygwin-1.7.8 , libgfortran3-4.3.4-4, lapack-3.2.2-2, qrupdate-qrupdate-1.1.1-1 broken (as also octave3.4.0-3) >> The full source is here, and it is a very tiny lib >> http://matzeri.altervista.org/cygwin-1.7/qrupdate/ > > Yes, well, are you going to debug this problem? yes but very slowly, my real job take me real busy and I have little spare time. > Corinna > Regards Marco -- 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
