This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: What to do with "*** recreate_mmaps_after_fork_failed" ?


Max,

On Wed, Mar 30, 2005 at 05:21:25PM +0100, 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?

Try rebaseall -v to determine if you rebased your DLLs into the range
used by the Cygwin DLL, 0x6100000 - ~0x6200000 (i.e, 0x6100000 +
Cygwin's image size + rebaseall's default offset).  Note this can
happen if you have a lot of Cygwin related DLLs installed on your
system.  If so, then you need to skip rebasing some of your DLLs.

Jason

-- 
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D  8784 1AFD E4CC ECF4 8EF6

--
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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]