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" ?


On Mar 30 18:14, Max Bowsher wrote:
> 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?

Sure.  Just read src/winsup/cygwin/how-to-debug-cygwin.txt.

If the mmaps couldn't be recreated then very likely because a DLL has been
loaded to this memory area.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          mailto:cygwin@cygwin.com
Red Hat, Inc.

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