[Monotone-devel] Roster-related crash (somewhat of an abuse?)

[Ethan Blanton]

Hi all,

Monotone does not seem to deal with extant but unreferenced rosters
which are regenerated by a new commit gracefully.  Viz:

mtn -d test.mtn db init
mkdir test
cd test
echo "Test to crash monotone" > test.txt
mtn -d ../test.mtn setup -b org.example.monotone.test
mtn add test.txt
mtn ci -m "Whatever"
>>> committed revision 0123...
mtn db kill_rev_locally 0123...
rm -r _MTN
mtn -d ../test.mtn setup -b org.example.monotone.newtest
mtn add test.txt
mtn ci -m "Whatever"
>>> Crash

monotone 0.32 (base revision: 3f0fa5c1d232d37d47f6436fe74919dd3cd003b1)
Running on          : Linux 2.6.17-11-generic #2 SMP Thu Feb 1 19:52:28 UTC 
2007 i686
C++ compiler        : GNU C++ version 4.1.2 20060928 (prerelease) (Ubuntu 
4.1.1-13ubuntu5)
C++ standard library: GNU libstdc++ version 20060928
Boost version       : 1_33_1
Changs since base revision:
unknown

(There may be a simpler way to generate this; that was my stab at
 simplification.  'mtn db regenerate_caches' fixes the problem, as
 does manually removing unreferenced files and rosters.)

Ethan

-- 
The laws that forbid the carrying of arms are laws [that have no remedy
for evils].  They disarm only those who are neither inclined nor
determined to commit crimes.
                -- Cesare Beccaria, "On Crimes and Punishments", 1764

signature.asc
Description: Digital signature