unhandled win32 exception in [hg update] = 2884

[Zorba]

Hi,

We are at changeset 13 in a project, and I recently had reason to revert to 
changeset 11 (as is my wont !) to see how the old project handled something, 
so I deleted all the files from the working dir (except .Hg dir of course) 
and ran a

> hg update -r11

..which worked fine, and threw what I presume was the old version of the 
project out into the working dir, which I copied off to a temporary 
deployment area to do my stuff. Now, the problem arises when I go back to 
the working directory and wish to resume. So I went in, deleted all files 
from the working dir (except .Hg folder) and ran

> hg update

Now this time I get a "Visual Studio Just-in-time Debugger" Window coming up 
saying "An unhandled win32 exception occurred in hg.exe [2884]". Which is 
very strange as I thought hg was written in python, not one of the .net 
languages !! I guess there must be some windows stuff, maybe DLL's that the 
python is calling into. As you'd expect, mercury doesn't copy any files into 
the working dir. Straight away I was concerned that the repo had been 
corrupted so I found the verify command and tried that:

S:\Hg\altmore.co.uk NJ>hg verify -v
repository uses revlog format 1
checking changesets
checking manifests
crosschecking files in changesets and manifests
checking files
5960 files, 14 changesets, 6936 total revisions

I presume this means everything is ok ? (though it was be reassuring if the 
output clarified this)
If so, thank gawd for that.

Some other info:

version = Mercurial Distributed SCM (version 1.1.1+20081229)
installed about six weeks ago, not changed recently

I think I did the [>hg update -r11] on Sunday 22/02/09 and it was today that 
I did the [>hg update] that failed.
(BTW Is there a "command log" I can look up to verify when I performed the 
first one ?)

I was trying to work out what might have changed on this PC. On Friday 20th 
I upgraded a trial version of Visual Studio 2008 to the full version. It 
took a while, so may have been installing newer versions of DLL's etc.

But that was Friday, and I think I had a successful run of >hg update on 
Sunday (though it would be nice to have a command log to be sure) !!

mystified, and concerned

Zorba