[Openmcl-devel] freshly built wx86cl64.exe crashes on start

Ron Garret ron at flownet.com
Fri Jan 6 20:52:56 PST 2023

> On Jan 6, 2023, at 2:20 PM, R. Matthew Emerson <rme at acm.org> wrote:
>> On Jan 6, 2023, at 2:01 PM, Bharat Shetty <bshetty at gmail.com> wrote:
>> Is there some place we can get more details on the start up code/low address stuff in lisp-kernel, LAP, level-0 etc.? The info in the current and old ccl manual at trac is bit high level.
> I think it would be best to figure out how to tell Windows to stop applying its disruptive protection settings rather than expend a lot of effort researching and possibly making a big CCL change that will, at best, result in the status quo but slightly worse.
> I think it’s reasonable for a process to want to have control over its address space.  I would be surprised if Windows stops allowing that.

Particularly since backwards-compatibility has been a bedrock design principle of Windows since before it was called Windows.


More information about the Openmcl-devel mailing list