public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug java/30641] gcj corrupted double-linked list (glibc detected) Date: Wed, 31 Jan 2007 22:34:00 -0000 [thread overview] Message-ID: <20070131223415.31898.qmail@sourceware.org> (raw) In-Reply-To: <bug-30641-14020@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from tromey at gcc dot gnu dot org 2007-01-31 22:34 ------- Thanks. That valgrind trace sure is interesting. Do you have a checking-enabled build? You could look for ENABLE_CHECKING in build/gcc/auto-host.h. I'm trying to narrow down which load in rewrite_reflection_indexes is the buggy one; with checking enabled I think a bad load by VEC_index ought to crash. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30641
next prev parent reply other threads:[~2007-01-31 22:34 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-01-30 15:28 [Bug java/30641] New: " msubs at philips dot org dot uk 2007-01-30 19:50 ` [Bug java/30641] " tromey at gcc dot gnu dot org 2007-01-31 10:28 ` msubs at philips dot org dot uk 2007-01-31 22:34 ` tromey at gcc dot gnu dot org [this message] 2007-02-01 8:45 ` msubs at philips dot org dot uk 2007-02-01 10:12 ` aph at gcc dot gnu dot org 2007-02-01 10:38 ` msubs at philips dot org dot uk 2007-02-01 10:44 ` aph at gcc dot gnu dot org 2007-02-01 10:54 ` msubs at philips dot org dot uk 2007-02-01 10:57 ` msubs at philips dot org dot uk 2007-02-01 11:24 ` aph at gcc dot gnu dot org 2007-02-01 11:25 ` msubs at philips dot org dot uk 2007-02-01 14:34 ` aph at gcc dot gnu dot org 2007-02-01 14:38 ` aph at gcc dot gnu dot org 2007-02-01 14:39 ` aph at gcc dot gnu dot org 2007-02-01 15:08 ` msubs at philips dot org dot uk 2007-02-01 16:59 ` tromey 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=20070131223415.31898.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=java-prs@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).