From: Charles W. <cwi...@us...> - 2010-01-11 23:52:22
|
Ingmar Koecher wrote: > We appear to have narrowed this down to the tsvncache.exe app which is > part of Tortoise. After killing this process, sh.exe doesn't seem to > core dump anymore. We'll have to do more testing to attribute this > 100% to that process, but so far it looks like this helped. > > We were operating / creating the build in a directory that was > previously checked out via Tortoise. > > Has anybody run into this before? Any ideas why/how this would > interfere with sh.exe? Dunno about Tortoise, but I want to clear up one misunderstanding. If the 'dodgy app' problem is biting you, it's USUALLY because some resident program like a virus scanner or firewall is "hooking" into every DLL's DllInit routine. This causes problems with cygwin/msys's emulation of "fork()", where we must ensure that the EVERY DLL is loaded in exactly the same location in the child's address space as it was in the parent's. This "hooking" behavior causes problems with this. Unfortunately, IF this bites you, you can't simply "disable" the offending program -- the hooks are still there; they just don't do anything. What you have to do is *remove* -- uninstall -- the dodgy app, so that it no longer "hooks" the DLL initialization. In your case, it appears that Tortoise may be causing problems via some OTHER mechanism that the one we typically see with "dodgy" apps. -- Chuck |