From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14833 invoked by alias); 20 Jul 2012 19:45:41 -0000 Received: (qmail 14815 invoked by uid 22791); 20 Jul 2012 19:45:40 -0000 X-SWARE-Spam-Status: No, hits=-3.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,KHOP_THREADED X-Spam-Check-By: sourceware.org Received: from localhost (HELO sourceware.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 20 Jul 2012 19:45:25 +0000 From: "tromey at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug python/14373] std::vector Date: Fri, 20 Jul 2012 19:45:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: python X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: CC Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org X-SW-Source: 2012-q3/txt/msg00085.txt.bz2 http://sourceware.org/bugzilla/show_bug.cgi?id=14373 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at redhat dot com --- Comment #1 from Tom Tromey 2012-07-20 19:45:24 UTC --- First, I agree it would be good to be able to interrupt gdb when it gets wedged like this. However, the problem here is that the varobj has many children -- in my test, 105312 of them (but obviously YMMV). Front ends are supposed to limit dynamic varobj output using the provided controls, like -var-set-update-range or the optional arguments to -var-list-children. Otherwise, bad things will happen. In this case, the vector is uninitialized, causing problems. But the same problems can occur due to other bugs in the program (trashing the heap), or just if the program happens to create a really huge data structure -- not unheard-of. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.