X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:cc:subject:message-id:references
	:mime-version:content-type:in-reply-to; q=dns; s=default; b=pRpm
	75X/8a+clWKSdkXZMV4IP8UhJrhHAJsEsqB+VUenRFuoesZvZZ6abe9oKhUQ0Y0X
	NmN71BfY7IFywvNzzmKyJegs2WHVkrFGCYyyjDoMo7GOM/K+GEE51kexWlm7T8dV
	yO1xYrK5z91zJ2MxBZs9L1mMPYkeINvzFHQsWJs=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:cc:subject:message-id:references
	:mime-version:content-type:in-reply-to; s=default; bh=18Vdm2YUyb
	iJ/osDGuVEK43fWkM=; b=MsFV6Ho63Z5dXwC+1Q4l7xS6Um9PiZwg2m6bNyxeH2
	zS7V/tQtKe29//pxZPzFf7ntFy9Oc9im8Sk7qNMTATVyiPJaWrtThBjrTFcFtWcF
	qxAXW1+yrJ9KTG1MLrKLqLUvJdBamK3MwxdnLQPMr3S4hjk6grca3vqdgNAsSWwN
	s=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Spam-SWARE-Status:	No, score=1.2 required=5.0 tests=AWL,BAYES_20,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	plunk.org
Date:	Tue, 8 Oct 2013 20:30:55 -0400
From:	Don Hatch <hatch AT plunk DOT org>
To:	cygwin AT cygwin DOT com
Cc:	Don Hatch <hatch AT plunk DOT org>
Subject:	Re: checking in >= 256k file fatally corrupts rcs file
Message-ID:	<20131009003055.GA30082@plunk.org>
References:	<20131008102204 DOT GB9241 AT plunk DOT org> <525499E5 DOT 4090608 AT etr-usa DOT com>
MIME-Version:	1.0
In-Reply-To:	<525499E5.4090608@etr-usa.com>
User-Agent:	Mutt/1.5.21 (2010-09-15)
X-IsSubscribed:	yes

On Tue, Oct 08, 2013 at 05:48:53PM -0600, Warren Young wrote:
> On 10/8/2013 04:22, Don Hatch wrote:
> >
> >Checking in a text file of size >= 256k
> >corrupts the rcs file, irretrievably losing most of the contents
> 
> It's documented in the rcs NEWS file:
> 
>     - Env var RCS_MEM_LIMIT controls stdio threshold.
> 
>       For speed, RCS uses memory-based routines for files up to
>       256 kilobytes, and stream-based (stdio) routines otherwise.
>       You can change this threshold value by setting the environment
>       variable ?RCS_MEM_LIMIT? to a non-negative integer, measured in
>       kilobytes.  An empty ?RCS_MEM_LIMIT? value is silently ignored.
> 
> So, use the new environment variable, or build up your huge diffs a
> few steps at a time, so as to avoid spamming this buffer.

Hi Warren,

Thanks for the pointer.

That quote certainly doesn't describe or justify the very serious
corruption bug I'm seeing in any way;
however, it seems very likely that the corruption bug
was introduced along with this new optimization feature
that you reference, so it's good information.

If it's indeed the case that this bug was introduced along with this
non-essential feature, it would be really good if the feature
could be backed out, and possibly re-introduced at a later time
after it has been re-worked so that doesn't break the product.

Don

-- 
Don Hatch
hatch AT plunk DOT org
http://www.plunk.org/~hatch/

--
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

- Raw text -