X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.7 required=5.0 tests=AWL,BAYES_20,RCVD_IN_DNSWL_NONE,UNPARSEABLE_RELAY X-Spam-Check-By: sourceware.org X-Yahoo-SMTP: jenXL62swBAWhMTL3wnej93oaS0ClBQOAKs8jbEbx_o- Date: Wed, 20 Apr 2011 21:06:57 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: rebaseall rebasing dlls into cygwin address range? Message-ID: <20110421010657.GA24483@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) 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 I just noticed today that cygz.dll was rebased right into the middle of cygwin1.dll's address range. So, I added a -v to the rebaseall run and saw that there were quite a few dlls stomping all over cygwin. I wonder if this explains why we're seeing problems which are not cured by rebase? Maybe rebase should detect where cygwin1.dll lives and avoid putting other DLLs there. But, for now, just setting the base to something higher: rebaseall -b 0x77000000 would solve some of the problems we've seen. I don't know if that stomps on system routines or not, though. cgf -- 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