X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-0.6 required=5.0 tests=AWL,BAYES_50,DKIM_SIGNED,DKIM_VALID,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Message-ID: <4DE41BB8.2000504@cwilson.fastmail.fm> Date: Mon, 30 May 2011 18:35:36 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666 MIME-Version: 1.0 To: Cygwin Mailing List Subject: Re: Problem with Cygwin's fdopen and Windows handles References: <20110529233841.GC5283@ednor.casa.cgf.cx> <20110530174649.GB14225@ednor.casa.cgf.cx> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On 5/30/2011 5:12 PM, Juanjo wrote: > It seems I did not express myself properly. Code is compiled on the fly. > DLLs do not survive beyond program execution. This is a dynamic language > (Common Lisp btw) and functions are compiled and run and consumed > quickly. Calling rebase for each invocation is overkill (it will scan the > whole system!) and I would not even know how to start assigning > fixed addresses to libraries myself. Well, one workaround is to use the --enable-auto-image-base flag when linking your ephemeral DLL. This generates a custom image base address based on a hash of the pathname of the DLL. There's no guarantee this doesn't clash with stuff, but at least it'll be *different* for dlls that have different names. Dunno of any solutions or recommendations related to the rest of your email, tho -- sorry. -- Chuck -- 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