http://d.puremagic.com/issues/show_bug.cgi?id=5176
--- Comment #20 from Don <[email protected]> 2013-01-10 01:14:30 PST --- (In reply to comment #18) > (In reply to comment #17) > > Windows inserts a "guard page" that is hardware protected beyond the end of > > the > > allocated stack. A stack overflow runs into that guard page, which throws a > > seg > > fault. > > > > It does not corrupt memory. > > What about the rest of the platforms? On our code (Linux only, derived from Tango, its basically the same as druntime) our fibers allocate a guard page at the end of the stack. We added this because we found that stack overflows in fibers are easy to create but difficult to debug. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------
