public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: gepeng@cheminfo.pku.edu.cn To: gcc-gnats@gcc.gnu.org Subject: c/7495: GCC generates crashing code when there is large static array Date: Mon, 05 Aug 2002 04:36:00 -0000 [thread overview] Message-ID: <20020805113231.16672.qmail@sources.redhat.com> (raw) >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:
next reply other threads:[~2002-08-05 11:36 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-08-05 4:36 gepeng [this message] 2003-03-11 22:37 neroden
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20020805113231.16672.qmail@sources.redhat.com \ --to=gepeng@cheminfo.pku.edu.cn \ --cc=gcc-gnats@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).