Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > gnu.bash.bug > #14697 > unrolled thread

Re: Segfault on recursive trap/kill

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Segfault on recursive trap/kill Mike Gerwitz <mtg@gnu.org> - 2018-10-07 13:24 -0400

#14697 — Re: Segfault on recursive trap/kill

[Multipart message — attachments visible in raw view] — view raw

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

[toc] | [standalone]

Back to top | Article view | gnu.bash.bug

csiph-web