On 5 September 2015 at 15:03, Giacomo Tesio <giac...@tesio.it> wrote:
> For extra safety I added an assert(*p == nil) just after rfork, and after > a few (apparently?) successful spawns, the assert fails. The stack is a logical copy of the parent process's stack at rfork, even with RFMEM, since the stack's not shared, so if you've previously assigned it in the parent, its child will see the non-nil value after the fork. It doesn't get a completely fresh stack.
