You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@subversion.apache.org by Daniel Shahaf <da...@elego.de> on 2012/03/25 19:18:53 UTC

Relation to mergeinfo-count corruption Re: #4129 is reproducible Re: predecessor count for the root node-revision is wrong message

(Just changing the subject so mergeinfo gurus spot this thread too.
tldr: #4129 also explains a bug whereby FSFS minfo-cnt values were set
to the value read from uninitialized memory (and which might therefore
have been smaller than the correct value).)

Philip Martin wrote on Fri, Mar 23, 2012 at 19:58:29 +0000:
> The commit fails because the count: is wrong, but if I disable that
> check to allow the commit to complete then I see a bogus minfo-cnt such
> as:
> 
> id: 0.0.r7/322
> type: dir
> pred: 0.0.r4/180
> count: 5
> text: 7 198 111 0 242bff40060f22bcf85959dcf552851a
> cpath: /
> copyroot: 0 /
> minfo-cnt: 43
> 
> Using the current trunk with the issue 4129 fix applied this no longer
> happens: I don't get the valgrind warnings and the minfo-cnt is correct.
> 
> -- 
> uberSVN: Apache Subversion Made Easy
> http://www.uberSVN.com