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

Groups > gnu.bash.bug > #14692 > 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 Robert Elz <kre@munnari.OZ.AU> - 2018-10-07 09:42 +0700

#14692 — Re: Segfault on recursive trap/kill

    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

[toc] | [standalone]

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

csiph-web