{"thread":{"id":"30837","subject":"git on 64bit windows - state of the art?","startedAt":"2012-06-19T08:40:56Z","lastAt":"2012-06-21T02:22:13Z","messageCount":12,"participants":["Jon Seymour","Erik Faye-Lund","Philippe Vaucher","Pascal Obry"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"193821","messageId":"CAH3AnrrzKycCGprrWxiu5S5fuTHA8-cuNTi14Wz5WdtG+6FNJA@mail.gmail.com","threadId":"30837","inReplyTo":null,"subject":"git on 64bit windows - state of the art?","fromName":"Jon Seymour","fromEmail":"jon.seymour@gmail.com","sentAt":"2012-06-19T08:40:56Z","receivedAt":"2012-06-19T08:40:56Z","isPatch":false,"sender":{"key":"jon.seymour@gmail.com","avatar":"https://avatars.githubusercontent.com/u/207131?v=4"},"body":"Hi,\n\nI was wondering what the state of the art for running git on 64 bit Windows is?\n\nI haven't tried it myself - my Windows VMs are 32bit - but colleagues\nare reporting persistent problems with the cygwin build because of\n(cygwin) rebasing issues [ the issue most often reveals itself as a\nfailure to fork subprocesses while executing git svn ]\n\nWe have tried to use cygwin's rebaseall to address the issue per the\nadvice on stackoverflow.com amongst other places, but this \"solution\"\ndoesn't seem to produce permanent results (even if the installed\ncygwin code base remains stable). We tried msysgit to see if this\nprovided any relief, but it had similar issues (perhaps because cygwin\nwas also active at the time - I haven't had a chance to diagnose this\nparticular more thoroughly yet).\n\nHas anyone got a recipe that provides a permanent and stable solution\nto the (cygwin) 32/64bit rebasing issues?\n\njon.\n"},{"id":"193822","messageId":"CABPQNSY_1adwYb2yhahpbFjdBBzygz+u6fNVnrXpwA7RsdZOCw@mail.gmail.com","threadId":"30837","inReplyTo":"CAH3AnrrzKycCGprrWxiu5S5fuTHA8-cuNTi14Wz5WdtG+6FNJA@mail.gmail.com","subject":"Re: git on 64bit windows - state of the art?","fromName":"Erik Faye-Lund","fromEmail":"kusmabite@gmail.com","sentAt":"2012-06-19T08:57:31Z","receivedAt":"2012-06-19T08:57:31Z","isPatch":false,"sender":{"key":"kusmabite@gmail.com","avatar":"https://avatars.githubusercontent.com/u/47073?v=4"},"body":"On Tue, Jun 19, 2012 at 10:40 AM, Jon Seymour wrote:\n> Hi,\n>\n> I was wondering what the state of the art for running git on 64 bit Windows is?\n\nGit for Windows. That goes both for 32 and 64-bit Windows.\n\n> We tried msysgit to see if this\n> provided any relief, but it had similar issues (perhaps because cygwin\n> was also active at the time - I haven't had a chance to diagnose this\n> particular more thoroughly yet).\n>\n\nI'm running Git for Windows (msysgit is the development environment\nfor Git for Windows) on all my development-systems (which are all\n64-bit) without any rebase-problems. I do not have Cygwin installed,\nthough.\n\nGit for Windows is pretty heavily tested on 64-bit.\n"},{"id":"193823","messageId":"CAGK7Mr62y4-fTFzuLGmuOd+zLkk+h1Q-rCb30TW3dWd8VLhhAw@mail.gmail.com","threadId":"30837","inReplyTo":"CAH3AnrrzKycCGprrWxiu5S5fuTHA8-cuNTi14Wz5WdtG+6FNJA@mail.gmail.com","subject":"Re: git on 64bit windows - state of the art?","fromName":"Philippe Vaucher","fromEmail":"philippe.vaucher@gmail.com","sentAt":"2012-06-19T08:59:37Z","receivedAt":"2012-06-19T08:59:37Z","isPatch":false,"sender":{"key":"philippe.vaucher@gmail.com","avatar":null},"body":"> I was wondering what the state of the art for running git on 64 bit Windows is?\n\nDid they try msysgit? In my experience it has way less issues than cygwin.\n\nPhilippe\n"},{"id":"193824","messageId":"CAH3AnrppdYOC_Z4PWnzNLWXPSSQMBvHd9KPnQyAt40=FTn2dFg@mail.gmail.com","threadId":"30837","inReplyTo":"CAGK7Mr62y4-fTFzuLGmuOd+zLkk+h1Q-rCb30TW3dWd8VLhhAw@mail.gmail.com","subject":"Re: git on 64bit windows - state of the art?","fromName":"Jon Seymour","fromEmail":"jon.seymour@gmail.com","sentAt":"2012-06-19T09:10:02Z","receivedAt":"2012-06-19T09:10:02Z","isPatch":false,"sender":{"key":"jon.seymour@gmail.com","avatar":"https://avatars.githubusercontent.com/u/207131?v=4"},"body":"On Tue, Jun 19, 2012 at 6:59 PM, Philippe Vaucher\n wrote:\n>> I was wondering what the state of the art for running git on 64 bit Windows is?\n>\n> Did they try msysgit? In my experience it has way less issues than cygwin.\n>\n> Philippe\n\nErik and Philippe,\n\nThanks for the quick responses. I'll take cygwin out of the picture\ncompletely and see if that improves things.\n\nI was hoping to use cygwin because I don't like the (understandable)\nlimitations of the msysgit toolset (restricted set of available tools,\ninvoking bat files is painful, symbolic links don't work the same way,\netc)\n\njon.\n"},{"id":"193825","messageId":"CAGK7Mr5byhUOZ1vZTOMWWBVs4rXdE8RH+SS2ppz2QP1e-MiG0w@mail.gmail.com","threadId":"30837","inReplyTo":"CAH3AnrppdYOC_Z4PWnzNLWXPSSQMBvHd9KPnQyAt40=FTn2dFg@mail.gmail.com","subject":"Re: git on 64bit windows - state of the art?","fromName":"Philippe Vaucher","fromEmail":"philippe.vaucher@gmail.com","sentAt":"2012-06-19T09:28:46Z","receivedAt":"2012-06-19T09:28:46Z","isPatch":false,"sender":{"key":"philippe.vaucher@gmail.com","avatar":null},"body":"> I was hoping to use cygwin because I don't like the (understandable)\n> limitations of the msysgit toolset (restricted set of available tools,\n> invoking bat files is painful, symbolic links don't work the same way,\n> etc)\n\nThere's a git bash with msysgit which is probably more limited than\ncygwin's one but decent enough. About the tools you can install\nsomething like https://github.com/bmatzelle/gow/wiki or\nhttp://gnuwin32.sourceforge.net.\n\nTo be honest most of the time I just use the *nix tools from the\nwindows command line, and jump into git bash for more advanced stuffs\nwhen necessary.\n\nPhilippe\n"},{"id":"193827","messageId":"CAH3AnromoeSc=34H14j92kFg3FjWbdg+XuZcd72Aq04zScvD8g@mail.gmail.com","threadId":"30837","inReplyTo":"CAGK7Mr5byhUOZ1vZTOMWWBVs4rXdE8RH+SS2ppz2QP1e-MiG0w@mail.gmail.com","subject":"Re: git on 64bit windows - state of the art?","fromName":"Jon Seymour","fromEmail":"jon.seymour@gmail.com","sentAt":"2012-06-19T09:49:38Z","receivedAt":"2012-06-19T09:49:38Z","isPatch":false,"sender":{"key":"jon.seymour@gmail.com","avatar":"https://avatars.githubusercontent.com/u/207131?v=4"},"body":"On Tue, Jun 19, 2012 at 7:28 PM, Philippe Vaucher\n wrote:\n>> I was hoping to use cygwin because I don't like the (understandable)\n>> limitations of the msysgit toolset (restricted set of available tools,\n>> invoking bat files is painful, symbolic links don't work the same way,\n>> etc)\n>\n> There's a git bash with msysgit which is probably more limited than\n> cygwin's one but decent enough. About the tools you can install\n> something like https://github.com/bmatzelle/gow/wiki or\n> http://gnuwin32.sourceforge.net.\n\nYes, I have tried the msysgit bash which is ok, except for the\nannoyances mentioned. Thanks for the additional links, which I shall\nperuse.\n\n>\n> To be honest most of the time I just use the *nix tools from the\n> windows command line, and jump into git bash for more advanced stuffs\n> when necessary.\n>\n\nI do like my bash and have got used to the way cygwin handles \"the divide\".\n\njon.\n"},{"id":"193828","messageId":"CAH3AnrpsG_XL1OpAtwu_rrMX8t5TRVGsp8yD14na1ktvKTDHDw@mail.gmail.com","threadId":"30837","inReplyTo":"CAH3AnromoeSc=34H14j92kFg3FjWbdg+XuZcd72Aq04zScvD8g@mail.gmail.com","subject":"Re: git on 64bit windows - state of the art?","fromName":"Jon Seymour","fromEmail":"jon.seymour@gmail.com","sentAt":"2012-06-19T09:57:01Z","receivedAt":"2012-06-19T09:57:01Z","isPatch":false,"sender":{"key":"jon.seymour@gmail.com","avatar":"https://avatars.githubusercontent.com/u/207131?v=4"},"body":"Would I be correct in assuming that Git For Windows doesn't support\n\"git svn\" because of the dependency on a perl implementation that is\navailable with msysgit but not (perhaps?) \"Git For Windows\"? Or is\nthis an incorrect assumption?\n\njon.\n"},{"id":"193832","messageId":"CABPQNSZyaW13pigA8eEnGo-7+-suVfDdvsGLj_04xTgaKfg4eg@mail.gmail.com","threadId":"30837","inReplyTo":"CAH3AnrpsG_XL1OpAtwu_rrMX8t5TRVGsp8yD14na1ktvKTDHDw@mail.gmail.com","subject":"Re: git on 64bit windows - state of the art?","fromName":"Erik Faye-Lund","fromEmail":"kusmabite@gmail.com","sentAt":"2012-06-19T11:02:25Z","receivedAt":"2012-06-19T11:02:25Z","isPatch":false,"sender":{"key":"kusmabite@gmail.com","avatar":"https://avatars.githubusercontent.com/u/47073?v=4"},"body":"On Tue, Jun 19, 2012 at 11:57 AM, Jon Seymour wrote:\n> Would I be correct in assuming that Git For Windows doesn't support\n> \"git svn\" because of the dependency on a perl implementation that is\n> available with msysgit but not (perhaps?) \"Git For Windows\"? Or is\n> this an incorrect assumption?\n\nThat's an incorrect assumption. Git for Windows ships with perl.\n"},{"id":"193864","messageId":"4FE0D02B.2040703@obry.net","threadId":"30837","inReplyTo":"CAH3AnrrzKycCGprrWxiu5S5fuTHA8-cuNTi14Wz5WdtG+6FNJA@mail.gmail.com","subject":"Re: git on 64bit windows - state of the art?","fromName":"Pascal Obry","fromEmail":"pascal@obry.net","sentAt":"2012-06-19T19:16:59Z","receivedAt":"2012-06-19T19:16:59Z","isPatch":false,"sender":{"key":"pascal@obry.net","avatar":"https://avatars.githubusercontent.com/u/467069?v=4"},"body":"Jon,\n\nThis is a known issue. I have since a long time left Windows world but I\nstill have some notes to \"fix\" this:\n\n>From the ash shell (be sure that no Cygwin process are still running):\n\n$ rebaseall\n$ peflagsall\n\nTry your command again. If it still doesn't work, try instead:\n$ rebaseall -b 0x50000000 -o 0x80000\nor -b 0xNNNN0000 where NNNN is any hex number between 2000 and 7000.\nThe -o option tell to leave more space between the dlls, it may also\nhelp. It did in my case.\n\nIf you are curious, look at /usr/share/doc/Cygwin/rebase-3.0.README\nfor more explanation.\n\n\nHope this helps.\n\nPascal.\n\n-- \n\n--|------------------------------------------------------\n--| Pascal Obry Team-Ada Member\n--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE\n--|------------------------------------------------------\n--| http://www.obry.net - http://v2p.fr.eu.org\n--| \"The best way to travel is by means of imagination\"\n--|\n--| gpg --keyserver keys.gnupg.net --recv-key F949BD3B\n"},{"id":"193916","messageId":"CAH3AnrqwUQkTAYHASgNMCTuCGFqsZUux44uhdMXGDGdJ9hV7oQ@mail.gmail.com","threadId":"30837","inReplyTo":"4FE0D02B.2040703@obry.net","subject":"Re: git on 64bit windows - state of the art?","fromName":"Jon Seymour","fromEmail":"jon.seymour@gmail.com","sentAt":"2012-06-20T02:10:45Z","receivedAt":"2012-06-20T02:10:45Z","isPatch":false,"sender":{"key":"jon.seymour@gmail.com","avatar":"https://avatars.githubusercontent.com/u/207131?v=4"},"body":"On Wed, Jun 20, 2012 at 5:16 AM, Pascal Obry wrote:\n> Jon,\n>\n> This is a known issue. I have since a long time left Windows world but I\n> still have some notes to \"fix\" this:\n>\n> From the ash shell (be sure that no Cygwin process are still running):\n>\n> $ rebaseall\n> $ peflagsall\n>\n> Try your command again. If it still doesn't work, try instead:\n> $ rebaseall -b 0x50000000 -o 0x80000\n> or -b 0xNNNN0000 where NNNN is any hex number between 2000 and 7000.\n> The -o option tell to leave more space between the dlls, it may also\n> help. It did in my case.\n>\n> If you are curious, look at /usr/share/doc/Cygwin/rebase-3.0.README\n> for more explanation.\n>\n>\n> Hope this helps.\n>\n> Pascal.\n\nThank you. I think we have tried the -b option without much luck, but\nI don't think we have tried the -o option.\n\nI will arrange to do some testing and will post to the list in a few\nweeks if this looks to be a definitive solution to the problem (or\notherwise)\n\njon.\n"},{"id":"193921","messageId":"4FE17465.4040501@obry.net","threadId":"30837","inReplyTo":"CAH3AnrqwUQkTAYHASgNMCTuCGFqsZUux44uhdMXGDGdJ9hV7oQ@mail.gmail.com","subject":"Re: git on 64bit windows - state of the art?","fromName":"Pascal Obry","fromEmail":"pascal@obry.net","sentAt":"2012-06-20T06:57:41Z","receivedAt":"2012-06-20T06:57:41Z","isPatch":false,"sender":{"key":"pascal@obry.net","avatar":"https://avatars.githubusercontent.com/u/467069?v=4"},"body":"Jon,\n\n> Thank you. I think we have tried the -b option without much luck, but\n> I don't think we have tried the -o option.\n> \n> I will arrange to do some testing and will post to the list in a few\n> weeks if this looks to be a definitive solution to the problem (or\n> otherwise)\n\nOk, the most important part is running peflagsall, this was the way to\nfix that properly on Win7 IIRC.\n\nPascal.\n\n-- \n\n--|------------------------------------------------------\n--| Pascal Obry Team-Ada Member\n--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE\n--|------------------------------------------------------\n--| http://www.obry.net - http://v2p.fr.eu.org\n--| \"The best way to travel is by means of imagination\"\n--|\n--| gpg --keyserver keys.gnupg.net --recv-key F949BD3B\n"},{"id":"194013","messageId":"CAH3AnrqRSKNgcZyYuyXSVjhaa9jzjQOEhbu_nVYt85g8FuJ9Jg@mail.gmail.com","threadId":"30837","inReplyTo":"CAMSUDdYxveE=FUSvSOLowVPWh7F24UtVFJr8zyc0ANhm0La6zA@mail.gmail.com","subject":"Re: git on 64bit windows - state of the art?","fromName":"Jon Seymour","fromEmail":"jon.seymour@gmail.com","sentAt":"2012-06-21T02:22:13Z","receivedAt":"2012-06-21T02:22:13Z","isPatch":false,"sender":{"key":"jon.seymour@gmail.com","avatar":"https://avatars.githubusercontent.com/u/207131?v=4"},"body":"On Thu, Jun 21, 2012 at 11:40 AM, Paul Harris wrote:\n>\n>\n> On 20 June 2012 14:57, Pascal Obry wrote:\n>>\n>> Jon,\n>>\n>> > Thank you. I think we have tried the -b option without much luck, but\n>> > I don't think we have tried the -o option.\n>> >\n>> > I will arrange to do some testing and will post to the list in a few\n>> > weeks if this looks to be a definitive solution to the problem (or\n>> > otherwise)\n>>\n>> Ok, the most important part is running peflagsall, this was the way to\n>> fix that properly on Win7 IIRC.\n>>\n>> Pascal.\n>>\n>\n> Hello,\n>\n> I use git + cygwin on Win7-64 (almost) without problems.  I have used\n> git-svn too (once) with success.\n\nWe do use git svn fairly heavily as part of our normal workflow and it\nis git-svn that is most heavily affected by the issue. If you only use\ngit-svn occasionally, it is possible that you have avoided the\nparticular issue we are facing. For us, git-svn does tend to work\nimmediately after the rebase or after a fresh boot when not much is\nloaded, but the reliability will be tend to degrade over time,\npresumably as the 32bit address space becomes more \"polluted\" by the\nother demands placed upon it.\n\n>\n> Perhaps Jon's is not working because rebaseall is not rebasing the\n> particular binaries he is using?  Perhaps his git svn is running some\n> binaries/dlls that are installed in non-standard locations?  Can that\n> happen?\n\nI don't think this is the case. All the users affected have a pretty\nstandard scripted cygwin install - there are no variations between\nusers and no special considerations for the SVN installation. We tried\nsome of the suggestions we found here about explicitly enumerating all\nthe .so and .dll files\n\n http://stackoverflow.com/questions/4988091/unable-to-start-solr-server-ruby-on-rails/6601464#6601464\n\nbut this didn't change the behaviour.\n\nI suspect the flavour of anti-virus solution one has installed may be\na factor. We are using Norton Antivirus.\n\nAnother factor might be the other tools we are running (Java IDEs and\napplication servers) although I haven't seen any good evidence one way\nor the other about whether the JVMs are actually a factor. As\nmentioned above, It does seem true that time since reboot is a factor,\nwhich is presumably related to how the 32bit address space is\n\"fragmented\" over time by the various demands placed on it.\n\nThus far, Pascal's solution seems to be working, but it is a bit early\nto call it a success yet - we will need several more days testing to\nbe sure.\n\njon.\n"}]}