From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28513 invoked by alias); 20 Dec 2011 14:29:22 -0000 Received: (qmail 28500 invoked by uid 22791); 20 Dec 2011 14:29:20 -0000 X-SWARE-Spam-Status: No, hits=-5.8 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 20 Dec 2011 14:29:03 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id pBKET2nw014880 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 20 Dec 2011 09:29:02 -0500 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id pBKET1vD005704; Tue, 20 Dec 2011 09:29:02 -0500 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id pBKET0HT031289; Tue, 20 Dec 2011 09:29:00 -0500 From: Tom Tromey To: Martin Runge Cc: gdb-patches@sourceware.org, asmwarrior Subject: Re: Fwd: [patch] avoid the crash of gdb+pretty printer on initialized local variables References: <4ED379D8.4060808@gmail.com> <4ED8534D.2050100@gmail.com> <4EDAD0B3.80505@gmail.com> Date: Tue, 20 Dec 2011 14:38:00 -0000 In-Reply-To: (Martin Runge's message of "Mon, 5 Dec 2011 11:13:25 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.92 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-12/txt/msg00659.txt.bz2 >>>>> "Martin" =3D=3D Martin Runge writes: Martin> I have seen gdb running into very long loops on Linux, too (Ubuntu Martin> 11.04, gdb 7.2 and 7.3). It looks like gdb is frozen, but it uses 1= 00% Martin> CPU. When attaching to that gdb process, I observed gdb fetching a = lot Martin> of values (address increasing, but the range was by far too large).= I Martin> guess this comes from a pretty printer, asking gdb to fetch too many Martin> values.=C2=A0libstdc++ and Qt4 pretty printers were in use in my ca= se. Martin> Although the error is probably somewhere in the pretty_printers, the Martin> user experience is very confusing. E.g. with Eclipse CDT on top, gdb Martin> does not respond to mi commands any more. As gdb does not give any Martin> "progress" of "still alive" messages via mi to Eclipse, it runs int= o a Martin> timeout and assumes gdb dead, debug session is broken and needs to = be Martin> restarted. Is Eclipse using the range limitation feature of dynamic varobjs? That is intended to help prevent this sort of thing. Martin> I think, only few people write their pretty printers themselves. Mo= st Martin> get them "somewhere from the Internet", so its hard to guarantee Martin> quality or rely on it. Yeah. Martin> Would it be a good idea in your eyes, if [...] I am not sure what would be the best solution, but could you file a bug report for the problem? Tom