Date: Sat, 06 Oct 2018 19:53:25 -0400
From: Mike Gerwitz <mtg@gnu.org>
Message-ID: <874ldy1vka.fsf@gnu.org>
| I haven't inspected the code to see if this is an access
| violation or if Bash is intentionally signaling SIGSEGV.
I expect that if you did look, you'd probably find that while
technically the former, it isn't a reference to some wild pointer,
but rather simply growing the stack until the OS says "no more"
and returns a SIGSEGV instead af allocating a new stack page.
kre