That's easily solved using some well-placed #ifdefs. Regards, Elias On 23 Aug 2015 19:49, "Blake McBride" <[email protected]> wrote:
> On Sun, Aug 23, 2015 at 3:53 AM, Elias Mårtenson <[email protected]> > wrote: > >> Normally you'd mark page on the stack as a redzone, triggering a >> segmentation fault when an attempt is made to access it. The signal handler >> can then determine that the redzone was reached, and throw the appropriate >> error when it happens. >> >> That way you don't have to check the stack size on every call. >> > > > I'd rather get strange errors when I exceed the stack size then do > anything not portable C++. > > --blake > > >
