public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl at lucon dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/12753] Memory corruption in cpp on bad input Date: Fri, 24 Oct 2003 07:39:00 -0000 [thread overview] Message-ID: <20031024064828.329.qmail@sources.redhat.com> (raw) In-Reply-To: <20031024064638.12753.hjl@lucon.org> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12753 ------- Additional Comments From hjl at lucon dot org 2003-10-24 06:48 ------- Created an attachment (id=4986) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=4986&action=view) A testcase (foo.c) This is the bad input which causes gcc 3.3.2 to dump core.
next prev parent reply other threads:[~2003-10-24 6:48 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-10-24 6:48 [Bug preprocessor/12753] New: " hjl at lucon dot org 2003-10-24 7:39 ` hjl at lucon dot org [this message] 2003-10-24 12:55 ` [Bug preprocessor/12753] [3.3,3.4 regression] " ehrhardt at mathematik dot uni-ulm dot de 2003-10-24 16:48 ` [Bug preprocessor/12753] [3.3/3.4 " pinskia at gcc dot gnu dot org 2003-12-20 20:23 ` pinskia at gcc dot gnu dot org 2003-12-24 21:31 ` gdr at gcc dot gnu dot org 2003-12-24 21:37 ` zack at gcc dot gnu dot org 2003-12-28 0:24 ` stl at caltech dot edu 2003-12-28 0:25 ` zack at gcc dot gnu dot org 2004-01-21 4:16 ` [Bug preprocessor/12753] [3.3/3.4/3.5 " gdr at gcc dot gnu dot org 2004-01-21 4:27 ` zack at codesourcery dot com 2004-02-15 12:36 ` gdr at gcc dot gnu dot org 2004-03-21 18:50 ` mmitchel at gcc dot gnu dot org 2004-06-01 4:26 ` zack at gcc dot gnu dot org 2004-06-09 19:22 ` mmitchel at gcc dot gnu dot org
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=20031024064828.329.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).