Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Message-ID: <061501c5354c$03310ce0$6508a8c0@robinson.cam.ac.uk> From: "Max Bowsher" To: References: <057401c53544$93402530$6508a8c0 AT robinson DOT cam DOT ac DOT uk> <20050330165502 DOT GB7144 AT cygbert DOT vinschen DOT de> Subject: Re: What to do with "*** recreate_mmaps_after_fork_failed" ? Date: Wed, 30 Mar 2005 18:14:39 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ X-Cam-AntiVirus: No virus found X-Cam-SpamDetails: Not scanned X-IsSubscribed: yes Note-from-DJ: This may be spam Corinna Vinschen wrote: > On Mar 30 17:21, Max Bowsher wrote: >> I ran into a DLL base address problem, and rebased. >> >> However, instead of fixing this, rebasing just changed the error message >> to >> this: >> >> 4 [main] ruby 2652 fhandler_disk_file::fixup_mmap_after_fork: >> requested 0x3F0000 != 0x0 mem alloc base 0x2F0000, state 0x1000, size >> 12288, Win32 error 487 >> M:\cygwin\bin\ruby.exe (2652): *** recreate_mmaps_after_fork_failed >> 3 [main] ruby 2716 fork_parent: child 2652 died waiting for dll >> loading >> /home/max/devel/subversion/trunk/subversion/bindings/swig/ruby/test/util.rb:48: >> [BUG] rb_sys_fail(fork(2)) - errno == 0 >> ruby 1.8.2 (2004-12-25) [i386-cygwin] >> >> >> How should I proceed? > > Debugging? Just an idea... Any hints? Max. -- 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/