Pages with no access to catch stack overflows?

[ColinH]

Would it be feasible to use a memory page with PROT_NONE at both the top and bottom of a coroutine stack to catch overflows immediately instead of after the fact in mco_yield()? I realise this would crash the application, hard, but that might be desirable for some use cases...

[edubart]

Yes, you can already do this with a custom allocator, outside this library. Note that you can also use the MCO_USE_VMEM_ALLOCATOR (if your OS supports it) and have large stack for every coroutine without really making RAM usage high. If you have a big stack, stack overflows are unlikely to happen.

[ColinH]

For the moment I hardwired a single PROT_NONE page at the bottom of the stack to reliably crash on stack overflow.

https://github.com/ColinH/mini-coro-plus/blob/87997010d62a50615505f2db8e9b4cbed3fff174/mini_coro_plus.ipp#L571