X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Sat, 20 Jun 2009 12:51:47 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: cygwin-1.7.0-50 Message-ID: <20090620165147.GB13175@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4A3C5B9B DOT 6060507 AT cwilson DOT fastmail DOT fm> <20090620040141 DOT GA12763 AT ednor DOT casa DOT cgf DOT cx> <20090620040544 DOT GA12818 AT ednor DOT casa DOT cgf DOT cx> <4A3C6D59 DOT 4030506 AT cwilson DOT fastmail DOT fm> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A3C6D59.4030506@cwilson.fastmail.fm> User-Agent: Mutt/1.5.19 (2009-01-05) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Sat, Jun 20, 2009 at 01:02:17AM -0400, Charles Wilson wrote: >Christopher Faylor wrote: >> On Sat, Jun 20, 2009 at 12:01:41AM -0400, Christopher Faylor wrote: >> And, just for the sake of accuracy, there should be fewer "unable to >> remaps" thanks to my 2009-06-07 change. > >Yeah -- now I remember Corinna tried a few things first, but then it was >your mod to use the cygheap for the "extra DLL data" rather than using >VirtualAlloc/NtCreateSection to put it "just after the DLL" that really >knocked that one down. > >Fewer "unable to remaps" -- yeah, I think we can say that... > >ZERO, is more like it! Woo hoo! Given the fact that I added the previous "add data after the dll was loaded" code, which apparently caused its share of remap problems, I think this particular "accomplishment" is pretty much a zero. cgf -- 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/