From: Daniel Colascione <dancol@dancol.org>
To: cygwin@cygwin.com
Subject: Re: clisp crashes on startup
Date: Fri, 13 Jul 2012 03:48:00 -0000 [thread overview]
Message-ID: <4FFF9A81.90403@dancol.org> (raw)
In-Reply-To: <4FFC4D3C.2010004@dancol.org>
[-- Attachment #1: Type: text/plain, Size: 1130 bytes --]
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_
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].
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 235 bytes --]
next prev parent reply other threads:[~2012-07-13 3:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 22:47 Daniel Colascione
2012-07-07 13:04 ` marco atzeri
2012-07-07 13:41 ` Daniel Colascione
2012-07-07 16:19 ` Reini Urban
2012-07-07 17:45 ` marco atzeri
2012-07-07 19:08 ` Daniel Colascione
2012-07-09 21:01 ` Reini Urban
2012-07-09 21:27 ` Daniel Colascione
2012-07-10 4:59 ` Daniel Colascione
2012-07-10 8:14 ` Corinna Vinschen
2012-07-10 15:42 ` Daniel Colascione
2012-07-13 3:48 ` Daniel Colascione [this message]
2012-07-13 7:41 ` Corinna Vinschen
2012-07-13 12:53 ` Reini Urban
2012-07-13 14:27 ` Corinna Vinschen
2012-07-13 16:30 ` Reini Urban
2012-07-13 17:46 ` Daniel Colascione
2012-07-07 17:05 ` Andrey Repin
2012-07-07 19:04 ` Daniel Colascione
2012-07-08 23:20 ` Andrey Repin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FFF9A81.90403@dancol.org \
--to=dancol@dancol.org \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).