Possible bug in text/binary mode handling in cygwin1.dll version1.5

[Vladimir Vysotsky <trivee at trivee dot org>]

Hi,

I'm using the following sequence of actions to reproduce this problem:

----------------
C:\test>bash
bash-2.05b$ echo "Test" >/c/test/test1.txt
bash-2.05b$ echo "Test" >c:/test/test2.txt
bash-2.05b$ ls -l
total 2
-rw-r--r--    1 vvysotsk mkpasswd        6 Oct 10 19:49 test1.txt
-rw-r--r--    1 vvysotsk mkpasswd        6 Oct 10 19:49 test2.txt
bash-2.05b$
----------------

Since drive C: is mounted in text mode (mount -f -s -t "c:" /c), both 
test1.txt and test2.txt are 6 bytes long ('T', 'e', 's', 't', 0x0D, 
0x0A). This is with cygwin1.dll version 1.3.2.

However, when I install cygwin1.dll version 1.5.x, test2.txt is only
5 bytes long, ending with just 0x0A:

----------------
C:\test>bash
bash-2.05b$ echo "Test" >/c/test/test1.txt
bash-2.05b$ echo "Test" >c:/test/test2.txt
bash-2.05b$ ls -l
total 2
-rw-r--r--    1 vvysotsk PCUsers         6 Oct 10 19:48 test1.txt
-rw-r--r--    1 vvysotsk PCUsers         5 Oct 10 19:48 test2.txt
bash-2.05b$
----------------

In other words, text mode is ignored if Windows-style path is
specified.

I'm concerned about this behavior because it breaks some 3rd party
tools that I'm using. In particular, a C compiler chokes on
multiline macros. As a result, I have to juggle between 1.5 (for normal
usage) and 1.3 (for running the tools that I've mentioned).

Could somebody please look into fixing this or suggest a workaround?

Best regards,
Vlad






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