public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zeratul976 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/51852] [regression] [c++11] tree check: expected tree_list, have HßèMÕþÿøtxøtsø
Date: Sat, 14 Jan 2012 10:02:00 -0000	[thread overview]
Message-ID: <bug-51852-4-51Tmj5Quvc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51852-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51852

--- Comment #8 from Nathan Ridge <zeratul976 at hotmail dot com> 2012-01-14 08:40:35 UTC ---
(In reply to comment #6)
> (In reply to comment #2)
> > you could also try building with --enable-checking=valgrind
> 
> When I try to build gcc with --enable-checking=valgrind, I get the following
> error:
> 
> --13242-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x2a
> 
> valgrind: m_debuginfo/readdwarf.c:2292 (copy_convert_CfiExpr_tree): Assertion
> 'srcix >= 0 && srcix < VG_(sizeXA)(srcxa)' failed.
> ==13242==    at 0x3802B1F7: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)

I built valgrind from source and ran cc1plus under valgrind (this is what
--enable-checking=valgrind would have done, right?).

Attached is the valgrind output. Is there anything helpful in there?


  parent reply	other threads:[~2012-01-14  8:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-13 20:26 [Bug c++/51852] New: " zeratul976 at hotmail dot com
2012-01-13 20:29 ` [Bug c++/51852] " paolo.carlini at oracle dot com
2012-01-14  0:54 ` redi at gcc dot gnu.org
2012-01-14  7:49 ` zeratul976 at hotmail dot com
2012-01-14  7:56 ` pinskia at gcc dot gnu.org
2012-01-14  8:12 ` zeratul976 at hotmail dot com
2012-01-14  8:14 ` zeratul976 at hotmail dot com
2012-01-14  9:56 ` zeratul976 at hotmail dot com
2012-01-14 10:02 ` zeratul976 at hotmail dot com [this message]
2012-01-16 10:19 ` rguenth at gcc dot gnu.org
2012-01-16 16:16 ` zeratul976 at hotmail dot com
2012-01-26 22:36 ` zeratul976 at hotmail dot com
2012-01-27  5:37 ` redi at gcc dot gnu.org
2012-01-27  6:29 ` pinskia at gcc dot gnu.org
2012-01-27  7:05 ` zeratul976 at hotmail dot com
2012-01-27  7:30 ` zeratul976 at hotmail dot com
2012-01-27  8:52 ` jason at gcc dot gnu.org
2012-01-27  9:02 ` zeratul976 at hotmail dot com
2012-01-27  9:12 ` jakub at gcc dot gnu.org
2012-01-27  9:33 ` jakub at gcc dot gnu.org
2012-01-27 19:45 ` jakub at gcc dot gnu.org
2012-01-27 20:25 ` zeratul976 at hotmail dot com
2012-01-27 20:26 ` jakub at gcc dot gnu.org
2012-01-29  0:46 ` paolo.carlini at oracle 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=bug-51852-4-51Tmj5Quvc@http.gcc.gnu.org/bugzilla/ \
    --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).