Re: Fwd: Updated: GraphicsMagick-1.3.12-2

hi, Cgf is waiting for a final confirmation that the latest pipe changes fix the issues reported in http://cygwin.com/ml/cygwin/2011-03/msg00186.html and, ultimately, http://cygwin.com/ml/cygwin/2011-03/msg00396.html I tested cygwin1-20110323.dll with different file sizes - the issue is fixed

Re: 1.7.8: write fails with EAGAIN

Hi, just re-tested this with cygwin1-20110313.dll. Here is the result (output of my "writetest" program): writing 78954543 bytes... result is 32505856, errno is 27 writing 46448687 bytes... result is -1, errno is 27 writing 46448687 bytes... result is -1, errno is 27 [ repeating a few hundred ti

Re: 1.7.8: write fails with EAGAIN

How about if you try a snapshot rather than your own home-built version? There is no snapshot dated 03-10 on http://cygwin.com/snapshots/. Unfortunately, there is no "hard limit" of 64MB. On the machine where I first encountered the error, the limit seems to be about 16MB. On another machine,

Re: 1.7.8: write fails with EAGAIN

Hi, tested with cvs HEAD: Just terminating the loop after write_overlapped_fallback is not enough. When the size to write exceeds MAX_OVERLAPPED_WRITE_LEN and WriteFile fails for MAX_OVERLAPPED_WRITE_LEN, write() will always return 0. Now any write with length > MAX_OVERLAPPED_WRITE_LEN fails

Re: 1.7.8: write fails with EAGAIN

I replaced the cygwin1.dll with cygwin1-20110309.dll and now a single write() with 78 MB never returns but seems to write repeatedly to the pipe (file was 5GB when I hit Ctrl-C). Just terminating the loop after write_overlapped_fallback is not enough. When the size to write exceeds MAX_OVERLAPPE

Re: 1.7.8: write fails with EAGAIN

I replaced the cygwin1.dll with cygwin1-20110309.dll and now a single write() with 78 MB never returns but seems to write repeatedly to the pipe (file was 5GB when I hit Ctrl-C). ... you don't want to keep_looping after calling write_overlapped_fallback ... -- Problem reports: http://cy

Re: 1.7.8: write fails with EAGAIN

> I've just uploaded a snapshot which attempts to work around this > problem. I ended up making some fairly substantial changes to the > pipe handling so this needs some serious testing, especially on > different platforms, e.g., XP, XP64, Windows 2008, etc. Oops.. I replaced the cygwin1.dll wi

Re: 1.7.8: write fails with EAGAIN

Surprisingly, this returns FALSE / nbytes = 0 / GetLastError = ERROR_INVALID_HANDLE on WinXP if the number of bytes exceeds some maximum and the handle refers to a pipe. Since you don't know what kind of handle you're writing to in write_overlapped, it seems reasonable to do the write in chunks.

Re: 1.7.8: write fails with EAGAIN

Hi, Hang on, you are saying that a *blocking* write(2) to a pipe returns with EAGAIN? Are you sure? It would be quite a surprise if git would actually do that. EAGAIN is only an expected error for non-blocking I/O, so applications which use blocking I/O usually only test for EINTR. I checke

Re: 1.7.8: write fails with EAGAIN

Hi, Hang on, you are saying that a *blocking* write(2) to a pipe returns with EAGAIN? Are you sure? It would be quite a surprise if git would actually do that. EAGAIN is only an expected error for non-blocking I/O, so applications which use blocking I/O usually only test for EINTR. since in

1.7.8: write fails with EAGAIN

Hi, recently, I found that cygwin-git was not able to 'cat-file' files that exceeded some size (in my case about 80MB). I tracked this down to the cygwin implementation of write() that behaves quite odd in some cases. I wrote a small program (source attached) that mmaps a given file and trie

Problems with libtool and libstdc++.la

Hello, i have a problem linking a DLL with libtool and -lstdc++. (using cygwin packages gcc 3.3.1-3 and libtool 1.5b-1) libtool complains that "This system can not link to static lib archive /usr/lib/libstdc++.la" Interestingly enough, if I turn off libtool's dependency lib checking (by setting