From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 127297 invoked by alias); 25 Mar 2019 13:24:51 -0000 Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org Received: (qmail 127285 invoked by uid 89); 25 Mar 2019 13:24:50 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=monitored, recursive, Recursive, online X-HELO: mail-wr1-f50.google.com Received: from mail-wr1-f50.google.com (HELO mail-wr1-f50.google.com) (209.85.221.50) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 25 Mar 2019 13:24:49 +0000 Received: by mail-wr1-f50.google.com with SMTP id p10so10162118wrq.1 for ; Mon, 25 Mar 2019 06:24:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=7Pg614g6X+0DCByfgVOFARlAoDdoe7aARwdLDYzYyQk=; b=esfnDzbV6SrizOiwXSYXRGCoZTlWctEp+dYffcaMD/S4LaybNHA1v8bCQqDebZH+5X pFPHfRYw7EeEsMSv1Q1KqVkMaS88fgNBDnz8D46/oKCf2jw2vHi4sw8vYWFQzCMSavHY zXgSSwRnZmBfurXOkr46El7Y9HnnF8eUnGMif1gwHG3bdJU6hM0N2qmF5nfcVVJusQyS NVcjzqjgbWT4GumCBDR9gmfz0e2P2xBgPov+0pesRz59pTIz0qyAkYPblCQvvYmvmmem 6kZWH/05jCuEySQwUSxn0ggseO7KqL5ZxCpM7qsm3PbndhW0YgTRA2yCtatwKoj6taum nIRQ== MIME-Version: 1.0 References: <1255ee27-882f-ab4e-ea45-ba6f35791b45@jguk.org> <877ecuikq9.fsf@mid.deneb.enyo.de> <835d09ce-752a-c0f7-e5cf-210e855df2ab@jguk.org> In-Reply-To: <835d09ce-752a-c0f7-e5cf-210e855df2ab@jguk.org> From: Jonathan Wakely Date: Mon, 25 Mar 2019 13:27:00 -0000 Message-ID: Subject: Re: Recursive SIGSEGV question To: Jonny Grant Cc: Florian Weimer , gcc-help Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2019-03/txt/msg00163.txt.bz2 On Mon, 25 Mar 2019 at 13:06, Jonny Grant wrote: > I had thoughts GCC would generate code that monitored the stack size and > aborted with a clear message when the stack size was exceeded. Looked > online, and it doesn't seem to be the case. That would add overhead that most people don't want.