public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/45201] ICE: stack overflow
Date: Wed, 11 Aug 2010 00:16:00 -0000 [thread overview]
Message-ID: <20100811001602.27284.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45201-19064@http.gcc.gnu.org/bugzilla/>
------- Comment #7 from pinskia at gcc dot gnu dot org 2010-08-11 00:16 -------
(In reply to comment #6)
> Created an attachment (id=21434)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21434&action=view) [edit]
> gdb backtrace
>
Hmm, GGC strikes again. Well really a small stack size on windows strikes with
GGC.
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |GC, ice-on-valid-code
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45201
next prev parent reply other threads:[~2010-08-11 0:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 21:51 [Bug c++/45201] New: ICE: stack overflow during debug information generation mr dot chr dot schmidt at online dot de
2010-08-05 21:53 ` [Bug c++/45201] " mr dot chr dot schmidt at online dot de
2010-08-05 21:54 ` mr dot chr dot schmidt at online dot de
2010-08-06 10:37 ` rguenth at gcc dot gnu dot org
2010-08-07 19:59 ` [Bug c++/45201] ICE: stack overflow mr dot chr dot schmidt at online dot de
2010-08-07 20:00 ` mr dot chr dot schmidt at online dot de
2010-08-07 20:01 ` mr dot chr dot schmidt at online dot de
2010-08-11 0:16 ` pinskia at gcc dot gnu dot org [this message]
2010-08-11 20:00 ` mr dot chr dot schmidt at online dot de
2010-08-11 20:01 ` mr dot chr dot schmidt at online dot de
[not found] <bug-45201-4@http.gcc.gnu.org/bugzilla/>
2010-12-11 16:08 ` davek at gcc dot gnu.org
2011-04-16 17:13 ` mr.chr.schmidt at online 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=20100811001602.27284.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).