From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4083 invoked by alias); 19 Oct 2012 10:55:32 -0000 Received: (qmail 4075 invoked by uid 22791); 19 Oct 2012 10:55:31 -0000 X-SWARE-Spam-Status: No, hits=-5.6 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from g1t0028.austin.hp.com (HELO g1t0028.austin.hp.com) (15.216.28.35) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 19 Oct 2012 10:55:28 +0000 Received: from G2W1953G.americas.hpqcorp.net (g2w1953g.austin.hp.com [16.238.8.185]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by g1t0028.austin.hp.com (Postfix) with ESMTPS id 9015E1C378; Fri, 19 Oct 2012 10:55:27 +0000 (UTC) Received: from G2W1954G.americas.hpqcorp.net (16.238.8.186) by G2W1953G.americas.hpqcorp.net (16.238.8.185) with Microsoft SMTP Server (TLS) id 14.2.283.4; Fri, 19 Oct 2012 10:54:43 +0000 Received: from G2W2431.americas.hpqcorp.net ([169.254.8.22]) by G2W1954G.americas.hpqcorp.net ([16.238.8.186]) with mapi id 14.02.0283.004; Fri, 19 Oct 2012 10:54:43 +0000 From: "Saraswati, Sujoy (JCTL-MCBS)" To: Tom Tromey CC: "gdb@sourceware.org" Subject: RE: Query regarding new dwarf type support in gdb Date: Fri, 19 Oct 2012 10:55:00 -0000 Message-ID: <5379BA8D7E9D7E4D87BF6749A92854C239426FF5@G2W2431.americas.hpqcorp.net> References: <5379BA8D7E9D7E4D87BF6749A92854C239425B12@G2W2431.americas.hpqcorp.net> <87wqynwkr6.fsf@fleche.redhat.com> In-Reply-To: <87wqynwkr6.fsf@fleche.redhat.com> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2012-10/txt/msg00088.txt.bz2 Hi Tom, Thanks for your reply. I have some further comment below - > I think gdb should issue a complaint (try "set complaints 1000") and > then make a new TYPE_CODE_ERROR type. >=20 > IIRC, g++ already emis rvalue references, but gdb doesn't handle them > yet. > You can see this in action by digging around in libstdc++, or maybe > using gdb with complaints enabled and "file -readnow ...". Ok, I could check the behavior. In general, is there any place where I can = check for current debug support of FSF gdb for C++11 features ? > We try to avoid calling 'error' during DWARF reading (not with complete > success) since it tends to discard the whole file's debuginfo -- much > too big a hammer. This area could use some fixes. Yes, I agree. It would be good if we could continue reading the rest of the= debug information from the file even if we face an unknown type. Regards, Sujoy > Tom