search for: stackoverflowguard

...the semantics and > implementation, then propose a "real attribute" once we've settled on a > workable implementation. > I seemed to have read that string attributes were for platform specific things, would that be incorrect? > - Pick a more generic name. Possibly "StackOverflowGuard"? > - Use two parameters. First, "minimum guard region size" (non-negative > integer number of bytes). Second, "test mechanism" (enum (FuncCall, Load, > Store, ConditionalCheck)). For the conditional check version, you'd need a > way to specify a failure...

The point of this is to cheaply detect all stack overflows using a guard page. For a guard page to actually detect all stack overflows, we need to ensure that the code touches each page of the stack in the right order, otherwise it could skip the guard page and write outside the stack. That is very bad for languages such as Rust which provides memory safety, so it currently does an explicit

...gt; > Generally, they're either a) platform specific, and b) prototyping > something. t.m.k. there is nothing that says a string attribute can't be > used long term, but generally, they don't seem to be. > > > > >> - Pick a more generic name. Possibly "StackOverflowGuard"? >> - Use two parameters. First, "minimum guard region size" (non-negative >> integer number of bytes). Second, "test mechanism" (enum (FuncCall, Load, >> Store, ConditionalCheck)). For the conditional check version, you'd need a >> way to sp...