X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-6.2 required=5.0	tests=AWL,BAYES_00,KHOP_PGP_SIGNED,KHOP_THREADED,SPF_HELO_PASS,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
Message-ID: <4FFF9A81.90403@dancol.org>
Date: Thu, 12 Jul 2012 20:48:17 -0700
From: Daniel Colascione <dancol@dancol.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: clisp crashes on startup
References: <4FF76A98.2020309@dancol.org> <4FF833DC.8090908@gmail.com> <4FF83C71.5000803@dancol.org> <CAHiT=DF+JfGcMVJ5x05cu1c7tZniRUfeTNNnBf4tzrHZq99+jA@mail.gmail.com> <4FF8759A.10400@gmail.com> <4FF88907.5060100@dancol.org> <CAHiT=DFvbMBSor+3cGQzpKE19YUHWH2uErkfGxcVOOAOt_J2sQ@mail.gmail.com> <4FFB4C82.7050702@dancol.org> <4FFBB6B3.2090705@dancol.org> <20120710081318.GB3051@calimero.vinschen.de> <4FFC4D3C.2010004@dancol.org>
In-Reply-To: <4FFC4D3C.2010004@dancol.org>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigEFDDE2A51EB66AB9AFDD766F"
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

--------------enigEFDDE2A51EB66AB9AFDD766F
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

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?
>=20
> 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_
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].


--------------enigEFDDE2A51EB66AB9AFDD766F
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAk//moYACgkQ17c2LVA10VuXegCdHXW9LMoE6CksWQbFrSZ1M7/K
XxoAoLF8NfAYR4MkY45lQzwRcijhErcW
=SMYw
-----END PGP SIGNATURE-----

--------------enigEFDDE2A51EB66AB9AFDD766F--
