From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: checking in >= 256k file fatally corrupts rcs file
Date: Wed, 09 Oct 2013 18:28:00 -0000 [thread overview]
Message-ID: <87ppreqoxq.fsf@Rainer.invalid> (raw)
In-Reply-To: <52555E65.1070000@cs.utoronto.ca>
Ryan Johnson writes:
> So in other words, a misguided performance optimization [1] that
> almost certainly has little measurable impact on performance [2] has
> introduced a silent data corruption bug (or tickled a latent one
> somewhere else). Lovely.
It is not the performance optimization that isn't working, but the code
path through plain stdio while doing a diff that was probably never
exercised (the tests all pass on Cygwin). Try RCS_MEM_LIMIT=0 to force
stdio. The error does not occur on Linux and it doesn't seem to be
known to the devs.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
--
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
next prev parent reply other threads:[~2013-10-09 18:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 10:16 Don Hatch
2013-10-08 23:49 ` Warren Young
2013-10-09 0:24 ` Don Hatch
2013-10-09 1:30 ` Warren Young
2013-10-09 2:07 ` Gary Johnson
2013-10-09 3:29 ` Warren Young
2013-10-09 6:59 ` Don Hatch
2013-10-09 13:37 ` Warren Young
2013-10-09 14:00 ` Ryan Johnson
2013-10-09 17:58 ` Don Hatch
2013-10-09 13:47 ` Ryan Johnson
2013-10-09 18:28 ` Achim Gratz [this message]
2013-10-09 20:57 ` Richard Gribble
2014-02-26 13:26 Wagemans, Peter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ppreqoxq.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).