From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14583 invoked by alias); 13 Jul 2012 18:38:48 -0000 Received: (qmail 14571 invoked by uid 22791); 13 Jul 2012 18:38:47 -0000 X-SWARE-Spam-Status: No, hits=-4.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,KHOP_THREADED X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 13 Jul 2012 18:38:34 +0000 From: "tromey at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/53477] pretty printer fails with: Python Exception list index out of range Date: Fri, 13 Jul 2012 18:38:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 3.1.x/3.2.x X-Bugzilla-Changed-Fields: Target Milestone Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2012-07/txt/msg01086.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53477 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |3.1.x/3.2.x --- Comment #1 from Tom Tromey 2012-07-13 18:38:18 UTC --- (Fixed the component) I can't reproduce this. I can print wordMapBitset before it is initialized but I get a different error: (gdb) p wordBitsetMap $4 = std::map with 140737488349518 elementsCannot access memory at address 0x68732f6c61636f7c ... which isn't pretty but is at least vaguely understandable as "GIGO". What version of gdb are you using? Can you do it with stack-printing enabled? ("set python print-stack on" in recent versions, somewhere under "maint" in older ones.) This might help.