X-Spam-Check-By: sourceware.org X-Mail-Handler: MailHop Outbound by DynDNS X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information) X-MHO-User: postmaster AT innobec DOT com Message-ID: <45AB899F.8090802@innobec.com> Date: Mon, 15 Jan 2007 09:03:11 -0500 From: Pierre Baillargeon User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: 1.7.0 CVS mmap failure Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SA-Do-Not-Run: IfYouSaySo X-SA-Exim-Connect-IP: 192.168.62.162 X-SA-Exim-Mail-From: pbaillargeon AT innobec DOT com X-SA-Exim-Scanned: No (on rodriguez); SAEximRunCond expanded to false Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 About the reason why the last 64K just before 2GB can't be used in Windows, I'll refer you to this post in The Old New Thing blog by Raymond Chen, who regularly discusses such obscure compatibility issues. See http://blogs.msdn.com/oldnewthing/archive/2003/10/08/55239.aspx. (Short answer: it has to do with address fixup when loading executable image and the influence of the alpha processor on the design.) -- 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/