X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Fri, 13 Jul 2012 09:40:09 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: clisp crashes on startup Message-ID: <20120713074009.GC26268@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <4FF83C71.5000803@dancol.org> <4FF8759A.10400@gmail.com> <4FF88907.5060100@dancol.org> <4FFB4C82.7050702@dancol.org> <4FFBB6B3.2090705@dancol.org> <20120710081318.GB3051@calimero.vinschen.de> <4FFC4D3C.2010004@dancol.org> <4FFF9A81.90403@dancol.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <4FFF9A81.90403@dancol.org> User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Jul 12 20:48, Daniel Colascione wrote: > On 7/10/12 8:41 AM, Daniel Colascione wrote: > > On 7/10/12 1:13 AM, Corinna Vinschen wrote: > >> On Jul 9 21:59, Daniel Colascione wrote: > >>> On 7/9/12 2:26 PM, Daniel Colascione wrote: > >>>> [snip] > >>> > >>> It turns out that clisp crashes only when I've rebased DLLs into the > >>> high portion of the 4GB WOW64 address space. > >> > >> Where did you rebase them to? You know that on WOW64 and with the > >> bigaddr flag on, the application heap is located at 0x80000000 by > >> default, right? Perhaps some of your DLLs just collide with that? > > > > I'm using a starting base address of 0xC8000000; I haven't had > > problems with any other program. > > It turns out that clisp uses bit 31 of each pointer for its gc mark > bit. No wonder the thing blows in bigaddr-aware mode. clisp _does_ Ouch. > work, however, when compiled with -DWIDE. In this mode, clisp uses two > words for each lisp value --- one for the pointer and one for the > metadata. Also, clisp has a LINUX_NOEXEC_HEAPCODES mode that also > works, and without bloating memory use, but that requires that no real > virtual address be in the range [0xC0000000, 0xDFFFFFFF]. That can't be guaranteed. WOW64 provides the full 32 bit VM address space. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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