From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5524 invoked by alias); 18 Mar 2003 00:16:01 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 5473 invoked by uid 71); 18 Mar 2003 00:16:01 -0000 Resent-Date: 18 Mar 2003 00:16:01 -0000 Resent-Message-ID: <20030318001601.5467.qmail@sources.redhat.com> Resent-From: gcc-gnats@gcc.gnu.org (GNATS Filer) Resent-Cc: gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org Resent-Reply-To: gcc-gnats@gcc.gnu.org, dank@kegel.com Received: (qmail 18037 invoked by uid 48); 18 Mar 2003 00:12:22 -0000 Message-Id: <20030318001222.18036.qmail@sources.redhat.com> Date: Tue, 18 Mar 2003 00:16:00 -0000 From: dank@kegel.com Reply-To: dank@kegel.com To: gcc-gnats@gcc.gnu.org X-Send-Pr-Version: gnatsweb-2.9.3 (1.1.1.1.2.31) Subject: c/10127: -fstack-check enforces wrong limit on main thread, works fine on other threads X-SW-Source: 2003-03/txt/msg01183.txt.bz2 List-Id: >Number: 10127 >Category: c >Synopsis: -fstack-check enforces wrong limit on main thread, works fine on other threads >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Tue Mar 18 00:16:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: dank@kegel.com >Release: gcc-2.9x, gcc-3.2 >Organization: >Environment: Red Hat 8.0, Pentium 3 >Description: Compiling the following program with -fstack-check int main(int argc, char **argv) { char foo[2417]; exit(0); } yields a SIGSEGV unless you reduce the size of foo below 2417 bytes. See http://www.kegel.com/stackcheck for full writeup. Workaround is to not use more than 2KB of stack in the main thread when compiling with -fstack-check. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: