help with debugging

[Adrian Buehlmann]

On 17.02.2010 00:51, varol kaptan wrote:
> Hi,
> 
> I have a weird problem:
> 
> Mercurial 1.4.3 / TortoiseHG 0.9.3, no extensions, winxp.
> 
> I am trying to commit a change in one file (~ 10Mb xls on winxp) and
> after about 5-10 seconds the command prompt comes back without any
> error message. A subsequent "hg status" reveals that the commit did
> not happen. There is an unfinished transaction and a wlock file in
> .hg/ (If I run the commit command again, mercurial advises me to run
> hg recover first.)
> 
> I've tried running hg with -v --debug --traceback without any success.
> Something obviously goes wrong at some point but nothing is displayed
> on the screen. The same commit succeeds on a linux box with Mercurial
> 1.2.1 if I copy the directory and remove the lock file(s). Version
> 1.2.1 on the xp box does not work either - same as 1.4.3.
> 
> Any suggestions on how to diagnose such a problem?

I do not assume that this is specifically related to your problem,
but, just to make sure:

Turn off the indexing service on the working copies and repositories,
and exclude them from virus scans.

http://bitbucket.org/tortoisehg/stable/wiki/Home#supported-platforms