unhandled win32 exception in [hg update] = 2884

[eg]

Martin Geisler wrote:
> "Zorba" <cr at altmore.co.uk> writes:
> 
> Hi Zorba,
> 
>> is the advice likely to be "re-install the latest version and cross
>> your fingers" ?
>>
>> I can see how this might work actually, if Visual Studio update has
>> over-written DLLs that Hg relied on, re-installing will revert them
>> back I guess...
>>
>> If reinstalling I would prefer to be installing TortoiseHg 0.6 (with
>> Mercurial 1.1.2), as I would like to try Tortoise.
> 
> I don't know why you're getting the Microsoft Visual Studio error, but I
> would try installing TortoiseHg.
> 

The reason you might get the Visual Studio debugger come up is due to 
the way Windows installs "just-in-time" or "post-mortem" debuggers. If 
you have Visual Studio installed it will register itself as the default 
debugger, so when an access violation, or other pertinent exceptions 
occur it will trigger.

It is unlikely that it has anything at all to do with the original 
error. If you want, you can change some registry settings and make 
another debugger (or Dr Watson) come up in its place in these 
situations. Don't let this side track you from the original cause of the 
problem.

For more gory details on debugger set up, see:

http://msdn.microsoft.com/en-us/library/cc266343.aspx

or

http://www.codeproject.com/KB/debug/windbg_part1.aspx

(look at the "just-in-time debugging" section in the above article)