Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
I have rebuilt my development environment on a new PC following crashes on my old PC. Now I am on a dual-core Pentium with 1Gb RAM and other new stuff. :-) But when I tested cvsnt out today I found a problem that originated in erroneous entries in the script files. What happened was this: I have a reference to CVSMailer in both loginfo and postcommand and I had forgotten to change the path in these after moving my folders around. So the scripts pointed to a non-existing folder. I first tried a cvs log command and it started but returned the output "script execution error" or the like. And WinCvs (from which I ran the cvs log command) did not get focus back until I clicked the red stop button to abort the execution. Then I fixed postcommand (which was the only script running for the log command). Next I tried committing the postcommand fix, but I got bitten by the same error message again, this time from loginfo of course. So now I had two aborted cvs calls. After fixing all of the script files I saw no more stops. Next I built an installer for 2081 and ran it only to find that it had problems installing CVSNT. After looking in TaskManager I saw two rogue cvs.exe processes still lingering on, probably from the scripting errors above. So I am questioning the cvs exception handling when executing the script files. It looks like there is an unhandled exception that causes cvs to abort the script function but also not completing the main task and just hang in there instead. It would be better if at least calls to potentially ill written scripts would not cause an exception exit to the idle loop or whatever cvs is doing in this case. Remember that wherever there are user entries there is a potential error and it should be cared for in code... /Bo (Bo Berglund, developer in Sweden)