Path: csiph.com!goblin3!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail From: Robert Elz Newsgroups: gnu.bash.bug Subject: Re: Segfault on recursive trap/kill Date: Sun, 07 Oct 2018 09:42:01 +0700 Lines: 15 Approved: bug-bash@gnu.org Message-ID: References: <874ldy1vka.fsf@gnu.org> <8736tj3llu.fsf@gnu.org> <25389056-9fcf-1d31-36d8-13098769a43a@case.edu> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: usenet.stanford.edu 1538880225 5920 208.118.235.17 (7 Oct 2018 02:43:45 GMT) X-Complaints-To: action@cs.stanford.edu Cc: Chet Ramey , bug-bash@gnu.org To: Mike Gerwitz Envelope-to: bug-bash@gnu.org In-Reply-To: <874ldy1vka.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2001:3c8:9009:181::2 X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Xref: csiph.com gnu.bash.bug:14692 Date: Sat, 06 Oct 2018 19:53:25 -0400 From: Mike Gerwitz 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