no "thread has overflowed its stack" messages on stack exhaustion within a stacker-created segment

[sunshowers]

Hi there, thanks for maintaining stacker!

Currently, on Linux x86_64, a simple stack exhaustion results in a message like:

thread 'main' has overflowed its stack
fatal runtime error: stack overflow

However, if stacker has created a stack segment, then no such message gets printed:

zsh: segmentation fault (core dumped)

This makes it somewhat harder to diagnose stack exhaustion issues.

I wrote a little program that tests a bunch of combinations: https://github.com/sunshowers/stack-exhaust-test. With this program, the issue is reproducible with:

cargo run -- --use-stacker once --red-zone $((16 * 1024 * 1024))

The ./run-commands.sh script runs the program with a bunch of flag combinations.

I'm not sure if it's possible to fix this (probably related, on Linux the program exits with SIGSEGV rather than SIGIOT) but it would be good to document this. Thanks again!

[nagisa]

Duplicate of #59

[sunshowers]

Thank you!