Disable (non-working) stack guard page protection on win32
... No more VirtualProtect error 0x1e7
... thanks to Alastair Bridgewater and Yaroslav Kavenchuk
;; In the event of a control-stack-exhausted-error, we
;; should have unwound enough stack by the time we get
;; here that this is now possible.
+ #!-win32
(sb!kernel::protect-control-stack-guard-page 1)
(funcall repl-fun noprint)
(critically-unreachable "after REPL"))))))))))
if(arch_os_thread_init(th)==0) return 1;
link_thread(th);
th->os_thread=thread_self();
+#ifndef LISP_FEATURE_WIN32
protect_control_stack_guard_page(1);
+#endif
#if defined(LISP_FEATURE_X86) || defined(LISP_FEATURE_X86_64)
return call_into_lisp_first_time(function,args,0);
;;; checkins which aren't released. (And occasionally for internal
;;; versions, especially for internal versions off the main CVS
;;; branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".)
-"0.9.11.45"
+"0.9.11.46"