Re: Segfault on recursive trap/kill

[Mike Gerwitz]

On Sun, Oct 07, 2018 at 09:42:01 +0700, Robert Elz wrote:
> 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.

That makes sense.  Thanks.

Though, it is an implementation detail that IMO a user of bash shouldn't
have to worry about---if bash instead implemented its interpreter stack
on the heap rather than the same stack as bash itself, a segfault could
have represented an actual bug.

-- 
Mike Gerwitz

signature.asc
Description: PGP signature