2014-07-02 03:58 AEST by Glen Starrett - When I have a sandbox that is set to a specific tag (e.g. cvs up -r TAG) then
try to switch to branch directly and the sandbox has renamed files, I get a crash.

Command is:
cvs -tttt up -r CVSNT_BRANCH_2_5_03_2382 > res.txt 2>&1

The first time I ran it I got a bunch of normal "P filename" messages along with
the other stuff, but it crashed here:

cvsnt server: Updating cvsgui
cvsnt server: cvsgui.cpp has been renamed to
cvs update: cvsgui.cpp not in entries file?
CVSNT crashed.
Writing crashdump.
Crashdump succeeded.  Zipping to "C:\Users\GLENST~1\AppData\Local\Temp\cvsnt-2.8
.01.5261-EUROPA-d5853b2e3353307-large.dmp.gz".
Crashdump complete.  %TEMP%\cvsnt-2.8.01.5261-EUROPA-d5853b2e3353307-large.dmp.g
z written.

I re-ran it with trace enabled, though server trace isn't enabled so I don't
know how much help it will be.  This time it crashed here:

11:39:34:   -> Rename_Entry(sspi_unix.cpp,(null))
cvs update: sspi_unix.cpp not in entries file?
11:39:34:   -> Exception caught - in minidumper
CVSNT crashed.

I'll attach that dump and trace output.  I've run it again, it's a different
file that it crashes on each time (gets past the previous crash point and stops
at the next renamed file).  Always with the "FILE has been remaned to" (with no
new filename at the end, think that's a big red flag).

Here's steps to reproduce every time with a smaller data set:
	Start in Scotty\cvsnt\cvsgui
	cvs up -dPCA
	cvs -q up -r CVSNT_2_8_01_5237
	cvs -q up -r CVSNT_BRANCH_2_5_03_2382
	>> See crash

Here's steps to NOT get the error:
	Start in Scotty\cvsnt\cvsgui
	cvs up -dPCA
	cvs -q up -r CVSNT_BRANCH_2_5_03_2382
	>> See files properly


L:\MH\Scotty\cvsnt>cvs ver
Client: Concurrent Versions System (CVSNT) 2.8.01 (Soolin) Build 5261 (client/se
rver)
Server: Concurrent Versions System (CVSNT) 2.8.02 (Cally) Build 4538 (RC 3) (cli
ent/server)