Subject: Re: cygwin: CR CR LF problem still there (was: Re: A dumb CR/LF question)
From: Christopher Faylor <[email-masked]>
To: Radek Tomis <[email-masked]>
Cc: [email-masked]
Date: Tue, 15 Jan 2002 14:32:44 -0500

Please check out the project web page for links to available information
and ports:  http://cygwin.com/ .

If you don't see what you need there, then the cygwin mailing list is
the best place to make observations or get questions answered.
Information on the mailing list is available at the project web page.

For your convenience, I've reset the Reply-To: address to point to the
cygwin mailing list.  I've also Cc'ed this reply there.

On Tue, Jan 15, 2002 at 08:26:25PM +0100, Radek Tomis wrote:
>> To: Cygwin <cygwin at sources dot redhat dot com>
>> Subject: Re: A dumb CR/LF question
>> From: Chris Faylor <cgf at cygnus dot com>
>> Date: Sat, 7 Oct 2000 14:16:22 -0400
>> References: <026101c03077$5a86a970$0600000a@tired>
>>
>> On Sat, Oct 07, 2000 at 09:57:54AM -0600, Dan Haynes wrote:
>> >I'm using 1.1.4 now, just upgraded from B20.1 which I've been using for
>> >a good long while.  I did a fresh install from the net about a week
>> >ago, using all defaults.  Now I do a:
>> >
>> >cat ./build/f1 ./build/f2 | sort >/tmp/f3
>> >
>> >Passing the output through some utiltities like 'sort' causes line
>> >endings to be expanded to CR CR LF (two carriage returns and a line
>> >feed)
>>
>> Thanks for the report.  It wasn't a dumb question at all.  I don't think
>> that you are the first to report this, but it finally sunk into my
>> feeble brain that there may be a problem here.
>>
>> I took some time to investigate this, and there is actually a problem in
>> the rewritten \r\n text handling code in cygwin.  It looks like the
>> problem has existed since 1.1.1.  The symptom is that when cygwin wrote
>> out a buffer, it would add a \r in front of any \n regardless of whether
>> the '\n' was already preceded by a \r or not.
>>
>> I've fixed this, so it will be in the next snapshot.  Please give it a
>> try. I'd like to nail this down for 1.1.5.
>>
>> Thanks for the bug report with a simple example that I could easily
>> duplicate.
>>
>> cgf
>
>Hello,
>
>Sorry to disturb you, I'm not quite sure what's worse, whether to contact
>you directly or subscribe to [email-masked] and report this bug
>that you've already fixed year ago. If I'm knocking at the wrong doors,
>please let me know.
>
>Anyway, the CR CR LF problem is present in Cygwin 1.3.5 (Nov 13 2001):
>
>echo hello > a.txt
>cat a.txt a.txt | sort > b.txt
>od -c b.txt
>
>0000000   h   e   l   l   o  \r  \r  \n   h   e   l   l   o  \r  \r  \n
>
>
>Do you happen to know why the bug is back ?
>Or maybe your snapshot fix didn't make it to the release version
>eventually ?
>
>I can use the tr -s '\r' as workaround, but it'd be much better to have
>working cygwin rather than keeping in mind this annoying bug.
>
>
>Excerpt from 'cygcheck':
>
>    Cygwin DLL version info:
>        DLL version: 1.3.5
>        DLL epoch: 19
>        DLL bad signal mask: 19005
>        DLL old termios: 5
>        DLL malloc env: 28
>        API major: 0
>        API minor: 47
>        Shared data: 3
>        DLL identifier: cygwin1
>        Mount registry: 2
>        Cygnus registry name: Cygnus Solutions
>        Cygwin registry name: Cygwin
>        Program options name: Program Options
>        Cygwin mount registry name: mounts v2
>        Cygdrive flags: cygdrive flags
>        Cygdrive prefix: cygdrive prefix
>        Cygdrive default prefix:
>        Build date: Tue Nov 13 23:16:25 EST 2001
>        CVS tag: cygwin-1-3-5-2
>        Shared id: cygwin1S3
>
>
>Thank you for your time.
>
>--
>Radek Tomis
>[email-masked]
>Help stop world hunger -- visit <http://www.thehungersite.org>
>Is The Hunger Site real? <http://www.umich.edu/~virus-busters/hunger.html>

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/