That is a risk, which is why you need to block all signals using the sigprocmask... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

Amanieu on June 7, 2015 | parent | context | favorite | on: Raw Linux Threads via System Calls

That is a risk, which is why you need to block all signals using the sigprocmask syscall before unmapping your stack.

geofft on June 7, 2015 [–]

Or you just don't have signal-handling functions. Signals only touch the stack if you handle them via functions. The default signal dispositions all either kill the process or do nothing, so they don't touch the stack.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact