On Sunday, 26 May 2013 at 18:43:30 UTC, Walter Bright wrote:
On 5/26/2013 8:43 AM, deadalnix wrote:
On Sunday, 26 May 2013 at 14:10:44 UTC, Paulo Pinto wrote:
Yeah, you are right. C and C++ stab themselves only to die a
few hours later
in a code section totally unrelated or just behave strangely.
Ha, I spent the day on an issue like that in D.
Stackoverflow on a fiber, that spill on a the stack of another
fiber. When the
other fiber unwind its stack enough to get to the trashed
data, SURPRISE !
Not really related to null pointer, but clearly a memory
safety issue.
Fibers should be implemented by mapping a 4K page with no
access rights at the end of each stack.
We do that in our code. Fibers are virtually unusable without it,
it is incredibly easy to get a stack overflow, and they are
horrible to debug.
