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


Groups > gnu.bash.bug > #14692

Re: Segfault on recursive trap/kill

From Robert Elz <kre@munnari.OZ.AU>
Newsgroups gnu.bash.bug
Subject Re: Segfault on recursive trap/kill
Date 2018-10-07 09:42 +0700
Message-ID <mailman.1780.1538880224.1284.bug-bash@gnu.org> (permalink)
References <874ldy1vka.fsf@gnu.org> <8736tj3llu.fsf@gnu.org> <25389056-9fcf-1d31-36d8-13098769a43a@case.edu>

Show all headers | View raw


    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

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread


Thread

Re: Segfault on recursive trap/kill Robert Elz <kre@munnari.OZ.AU> - 2018-10-07 09:42 +0700

csiph-web