|
CygwinDllRemappingFailure
Handling repeated failures of rebaseall to allow cygwin remaps IntroductionSometimes DLLs over which cygwin has no control get mapped into cygwin processes at locations that cygwin has chosen for its libraries. This has been seen primarily with anti-virus DLLs. When this occurs, cygwin must be instructed during the rebase to avoid the area of memory where that DLL is mapped. BackgroundSome background for this is available on http://www.dont-panic.cc/capi/2007/10/29/git-svn-fails-with-fatal-error-unable-to-remap/ Because of unix fork semantics (presumably), cygwin libraries must be mapped in the same location in both parent and child of a fork. All cygwin libraries have hints in them as to where they should be mapped in a processes address space; if those hints are followed, each library will be mapped in the same location in both address spaces. However, Windows is perfectly happy mapping a DLL anywhere in the address space; the hint is not considered controlling. The remapping error occurs when a cygwin process starts and one of its libraries cannot be mapped to the location specified by its hint. /usr/bin/rebaseall changes the DLL hints for all of the cygwin libraries so that there are no inter-library conflicts; it does this by choosing a contiguous but not overlapping library layout starting at a base address and working down. This process makes sure there are no intra-cygwin conflicts, but cannot deal with conflicts with external DLLs that are in cygwin process address spaces (e.g. anti-virus DLLs). To handle this case, you need to figure out what the problematic non-cygwin library is, where it is in the address space, and do the rebase all so that no cygwin hints map libraries to that location. Details
|
For Vista, you might want to use Process Explorer (http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx) instead of ListDLLs, and list the DLLs in the lower pane while selecting bash.exe as the process.
ListDLLs won't run unless you have DEBUG privileges on your account.
I started having this problem and was having a very hard time correcting it. One of two things fixed it (hard to say which, because they changed at the same time). 1) rebaseall was reporting an error "FixImage? (/usr/some file - happened to be mingw related) with last error = 13" 2) I uninstalled a bunch of cygwin stuff that I didn't need, including mingw stuff.
Nice explanation, but ...
don't you mean "higher than its starting address" instead of lower?
Thanks, Richard
Thankyou. Find puplished chromium cod and instayled