public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dhazeghi at yahoo dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/13757] -fstack-check causes segfaults Date: Wed, 21 Jan 2004 06:22:00 -0000 [thread overview] Message-ID: <20040121062220.21930.qmail@sources.redhat.com> (raw) In-Reply-To: <20040120042951.13757.duncan_roe@acslink.net.au> ------- Additional Comments From dhazeghi at yahoo dot com 2004-01-21 06:22 ------- Confirmed with mainline. You have to run the testcase a few times, but on one, it'll inevitably crash. Only options needed to reproduce are "-fstack-check" -- What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed| |1 Keywords| |wrong-code Last reconfirmed|0000-00-00 00:00:00 |2004-01-21 06:22:17 date| | Summary|-fstack-check can crash |-fstack-check causes |Hello World |segfaults http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13757
next prev parent reply other threads:[~2004-01-21 6:22 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-01-20 4:30 [Bug c/13757] New: -fstack-check can crash Hello World gcc-bugzilla at gcc dot gnu dot org 2004-01-20 4:38 ` [Bug c/13757] " pinskia at gcc dot gnu dot org 2004-01-21 6:22 ` dhazeghi at yahoo dot com [this message] 2004-08-04 11:36 ` [Bug other/13757] -fstack-check causes segfaults karsten_burger at gmx dot de
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=20040121062220.21930.qmail@sources.redhat.com \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).