From: Nikodemus S. <tsi...@cc...> - 2004-09-14 18:19:55
|
I've committed a fix for this in 0.8.14.24, one what should handle the tricky cases involving programmatic control or returning from previous frames (via the debugger feature) as well: When the control stack guard page is hit and unprotected the page immediately before it on stack is protected, so that either on our way down the stack -- or back up towards a new exhaustion for that matter -- it is hit. This results in the real guard page being protected and the "return guard page" being unprotected once again. Cheers, -- Nikodemus Schemer: "Buddha is small, clean, and serious." Lispnik: "Buddha is big, has hairy armpits, and laughs." |