Nope. Guard zones, not guard page (singular!). Except in the face of loading things from dynamic libs at runtime (which is unsafe right now anyway), you can always determine the maximum stack frame used by a given executable crate.
On Mon, Oct 21, 2013 at 8:37 PM, Keegan McAllister <kmcallis...@mozilla.com> wrote: >> * Consider switching to guard pages for the stack check > > What if your overflowing stack frame is bigger than a page and you access the > far end of it first? I think we'd still need __morestack checks for > functions that use a lot of stack. > > keegan > _______________________________________________ > Rust-dev mailing list > Rust-dev@mozilla.org > https://mail.mozilla.org/listinfo/rust-dev _______________________________________________ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev