Hi, On Mon, 15 Oct 2007, Brian Dessent wrote: > Johannes Schindelin wrote: > > > My bigger concerns are the performance and stability. For example, I > > had a very annoying problem on one of the machines I am testing > > msysGit on. The problem was _only_ fixable by deactivating component > > of Logitech's WebCam driver! Now, if a user-installable 3rd party > > program can make my regular git crash, I am scared what more it can > > do. > > That is because the MSYS runtime is based on an old version of Cygwin, > and it uses the same dirty tricks to emulate fork. These tricks rely on > having a repeatably consistent memory layout for a process each time it > is started, and when third party tools add hooks that affect the load > order or otherwise screw with the layout, the fork emulation fails. This > is also why it is sometimes necessary to assign unique base addresses to > all libraries (rebaseall) in order to get fork emulation working again. Ah, thanks for the explanation! (I knew that this thread still had something useful in it ;-) > So yes, it is unfortunate that some system tools can drastically affect > the ability of Cygwin and MSYS to function, but it's what we live with > to have fork/exec emulation. I see that there is work afoot to abstract > process creation so that hopefully this won't be as much a concern in > the near future. We never had the problem in git itself, since we never used fork() on Windows. The problem lies in our usage of bash and perl. Bash we can fix in the long run (this goes under the keyword "builtinification" on the git list), but I do not see our reliance on Perl going away, not for git {send-email,cvsimport,cvsexportcommit,svn}. These are not too common operations, so common users will be able to do without them. However, if you rely on the CVS/SVN connectors, or send-email, and in any case in the short run, you better run Git on Windows only when that funny Logitech driver is disabled ;-) Ciao, Dscho - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html