public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "eshkinkot at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/34934] -O1 crash compile *** glibc detected *** /usr/lib/gcc/i486-linux-gnu/4.2.3/cc1: double free or corruption (!prev)
Date: Wed, 23 Jan 2008 04:02:00 -0000 [thread overview]
Message-ID: <20080123030503.19359.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34934-15677@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from eshkinkot at gmail dot com 2008-01-23 03:05 -------
Created an attachment (id=15001)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15001&action=view)
gcc -save-temps -v -W -Wall -O2 -c send_tiny.c
preprocessed file
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34934
next prev parent reply other threads:[~2008-01-23 3:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 3:26 [Bug c/34934] New: " eshkinkot at gmail dot com
2008-01-23 4:02 ` eshkinkot at gmail dot com [this message]
2008-01-23 4:39 ` [Bug c/34934] " eshkinkot at gmail dot com
2008-01-23 8:55 ` [Bug middle-end/34934] " Ralf dot Wildenhues at gmx dot de
2008-01-23 8:55 ` Ralf dot Wildenhues at gmx dot de
2008-01-23 10:57 ` rguenth at gcc dot gnu dot org
2008-01-23 17:50 ` Ralf dot Wildenhues at gmx dot de
2008-01-23 22:22 ` rguenth at gcc dot gnu dot org
2008-01-23 22:41 ` Ralf dot Wildenhues at gmx dot de
2008-01-24 10:59 ` rguenth at gcc dot gnu dot org
2008-01-24 11:20 ` [Bug middle-end/34934] [4.1/4.2/4.3 Regression] " pinskia at gcc dot gnu dot org
2008-01-24 11:48 ` rguenth at gcc dot gnu dot org
2008-01-24 12:03 ` jakub at gcc dot gnu dot org
2008-01-24 15:42 ` jakub at gcc dot gnu dot org
2008-01-24 16:38 ` [Bug middle-end/34934] [4.1/4.2 " jakub at gcc dot gnu dot org
2008-07-04 22:30 ` [Bug middle-end/34934] [4.2 " jsm28 at gcc dot gnu dot org
2009-03-31 15:02 ` jsm28 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=20080123030503.19359.qmail@sourceware.org \
--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: link
Be 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).