X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: Date: Thu, 30 Oct 2008 22:07:19 -0700 From: "George Reilly" To: Cygwin Subject: git-svn: perl child_copy: linked dll data write copy failed In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Resending. I think the earlier copy failed to get through because it was HTML. It'd be nice if the mailing list software sent a rejection notice instead of silently dropping HTML mail on the floor. ---------- Forwarded message ---------- From: George Reilly Date: 2008/10/30 Subject: git-svn: perl child_copy: linked dll data write copy failed To: Cygwin I installed Cygwin from scratch today on my Vista SP1 box, using the v2.573.2.3 setup.exe. I ran "ash rebaseall -v", which worked once I renamed cyglsa64.dll to a different extension. "git init" works, as does "git status" and "git svn help". But "git svn init" spews (slowly) $ git svn init 4 [main] perl 5624 child_copy: linked dll data write copy failed, 0x6FEB60 00..0x6FEB6080, done 0, windows pid 5624, Win32 error 487 5022480 [main] perl 5624 child_copy: linked dll data write copy failed, 0x6FEB60 00..0x6FEB6080, done 0, windows pid 5624, Win32 error 487 10036887 [main] perl 5624 child_copy: linked dll data write copy failed, 0x6FEB6 000..0x6FEB6080, done 0, windows pid 5624, Win32 error 487 [etc, etc] Error 487 is ERROR_INVALID_ADDRESS, Attempt to access invalid address. I used SysInternals' Process Monitor, filtering on everything with "cygwin" in the path. Nothing obvious. I turned off Windows Defender. No dice. There is no antivirus software on this box. I looked at process 5624 in Process Explorer. The only DLLs in the process belong to Microsoft or Cygwin. (BTW, you really ought to build all your DLLs with good version resources, including Description, Company Name, and Version.) Now what? git-svn support seems to be even more broken in MSysGit. I'm currently experimenting with http://www.selenic.com/mercurial/wiki/index.cgi/SubversionToMercurialHowto as a DVCS-Subversion bridge, since I'm stymied with git-svn on Windows. -- /George V. Reilly george DOT v DOT reilly AT gmail DOT com http://www.georgevreilly.com/blog http://blogs.cozi.com/tech -- /George V. Reilly george AT reilly DOT org http://www.georgevreilly.com/blog http://blogs.cozi.com/tech -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/