marco atzeri writes: > See > http://cygwin.com/faq.html > at > 4.44. How do I fix fork() failures? > > and related > /usr/share/doc/rebase/README >
Just one question to this point. I know all this documentation - but I was pointed by C. Vinschen in http://cygwin.com/ml/cygwin/2012-02/msg00092.html not to use peflagsall. I know all the tools - rebase, rebaseall, peflags, peflagsall, perlrebase. They should be used when having fork failures. What's the correct way of using these tools. I know - I have to use rebaseall to resolve address layout conflicts! This is really clear and it has to be run. But what's about peflagsall - setting dynamicebase (ASLR) for DLLs. And whats about perlrebase? It uses another lower! address space and put perl and all perl related DLLs together in this address space and is removing dynamicbase (ASLR) for these DLLs. So - this all together is confusing me ... Can you tell me your opinion. best regards Heiko -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
