From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17024 invoked by alias); 5 Aug 2002 11:36:07 -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 16998 invoked by uid 71); 5 Aug 2002 11:36:05 -0000 Resent-Date: 5 Aug 2002 11:36:05 -0000 Resent-Message-ID: <20020805113605.16997.qmail@sources.redhat.com> Resent-From: gcc-gnats@gcc.gnu.org (GNATS Filer) Resent-To: nobody@gcc.gnu.org Resent-Cc: gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org Resent-Reply-To: gcc-gnats@gcc.gnu.org, gepeng@cheminfo.pku.edu.cn Received: (qmail 16673 invoked by uid 61); 5 Aug 2002 11:32:31 -0000 Message-Id: <20020805113231.16672.qmail@sources.redhat.com> Date: Mon, 05 Aug 2002 04:36:00 -0000 From: gepeng@cheminfo.pku.edu.cn Reply-To: gepeng@cheminfo.pku.edu.cn To: gcc-gnats@gcc.gnu.org X-Send-Pr-Version: gnatsweb-2.9.3 (1.1.1.1.2.31) Subject: c/7495: GCC generates crashing code when there is large static array X-SW-Source: 2002-08/txt/msg00085.txt.bz2 List-Id: >Number: 7495 >Category: c >Synopsis: GCC generates crashing code when there is large static array >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: support >Submitter-Id: net >Arrival-Date: Mon Aug 05 04:36:02 PDT 2002 >Closed-Date: >Last-Modified: >Originator: gepeng@cheminfo.pku.edu.cn >Release: gcc-3.0 >Organization: >Environment: nearly every platform including sun 6.5, irix 6.3 linux redhat 7.2 cygnus win32 >Description: when there is large static arrays in my program, GCC tends to generate crashing codes which will recieve SIGSEGV. when debugged, the crashing instruction is always refering to $esp, within the several lines after main(), suggesting stack and/or heap management error. as we got the program from others and it is too much trouble to change arrays from static to dynamic, could you suggest me any alternative way to fix it? the CC on sgi o2 workstation under irix 6.3 does not generate crashing codes when compiling the same program. thanks, Mannester GE >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: