public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jv244 at cam dot ac dot uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/36037] [4.4 regression] segfault in gt_ggc_mx_dw_loc_descr_struct
Date: Mon, 30 Jun 2008 06:23:00 -0000 [thread overview]
Message-ID: <20080630062253.24524.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36037-10259@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from jv244 at cam dot ac dot uk 2008-06-30 06:22 -------
(In reply to comment #6)
> It looks like you run out of stack space during GC walk. You can check if so
> by raising the stack limit with 'ulimit -s unlimited'.
current trunk (actually a few days old) doesn't fail anymore. The script used
for testing actually has ulimit -s 128000 which is pretty high. I tested with
ulimit -s 32000 and ulimit -s 64000, but couldn't get a crash.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36037
next prev parent reply other threads:[~2008-06-30 6:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 14:47 [Bug middle-end/36037] New: " fxcoudert at gcc dot gnu dot org
2008-05-05 5:25 ` [Bug debug/36037] " pinskia at gcc dot gnu dot org
2008-05-07 8:46 ` jv244 at cam dot ac dot uk
2008-05-07 10:18 ` fxcoudert at gcc dot gnu dot org
2008-05-18 17:52 ` [Bug middle-end/36037] " jv244 at cam dot ac dot uk
2008-05-18 17:59 ` jv244 at cam dot ac dot uk
2008-05-30 7:41 ` jv244 at cam dot ac dot uk
2008-06-25 12:01 ` rguenth at gcc dot gnu dot org
2008-06-25 12:06 ` jakub at gcc dot gnu dot org
2008-06-30 6:23 ` jv244 at cam dot ac dot uk [this message]
2008-07-03 6:10 ` ubizjak at gmail dot com
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=20080630062253.24524.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).