From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 84265 invoked by alias); 21 May 2015 10:00:33 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 84244 invoked by uid 89); 21 May 2015 10:00:32 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,SPF_HELO_PASS,T_RP_MATCHES_RCVD autolearn=no version=3.3.2 X-Spam-User: qpsmtpd, 2 recipients X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Thu, 21 May 2015 10:00:31 +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 (Postfix) with ESMTPS id 7188D91748; Thu, 21 May 2015 10:00:30 +0000 (UTC) Received: from localhost (ovpn-116-129.ams2.redhat.com [10.36.116.129]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t4LA0T78005834; Thu, 21 May 2015 06:00:29 -0400 Date: Thu, 21 May 2015 10:37:00 -0000 From: Jonathan Wakely To: =?iso-8859-1?Q?Fran=E7ois?= Dumont Cc: "libstdc++@gcc.gnu.org" , gcc-patches Subject: Re: Demangle symbols in debug assertion messages Message-ID: <20150521100028.GM30202@redhat.com> References: <5547D73C.6070602@gmail.com> <20150520101743.GH30202@redhat.com> <20150520101957.GI30202@redhat.com> <555CE461.5000106@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <555CE461.5000106@gmail.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-SW-Source: 2015-05/txt/msg01938.txt.bz2 On 20/05/15 21:45 +0200, François Dumont wrote: >On 20/05/2015 12:19, Jonathan Wakely wrote: >Does this fix https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65392 ? >> >With the patch this code of the bug report generates the following >debug message: > >/home/fdt/dev/gcc/build/x86_64-unknown-linux-gnu/libstdc++-v3/include/debug/safe_iterator.h:395: > error: attempt to retreat a past-the-end iterator 2 steps, which falls > outside its valid range. > >Objects involved in the operation: >iterator @ 0x0x7fff32365c50 { > type = >__gnu_debug::_Safe_iteratorint*>, std::__debug::deque > > (mutable >iterator); > state = past-the-end; > references sequence with type `std::__debug::dequestd::allocator >' @ 0x0x7fff32365cd0 >} > >which looks nice. > >However I wouldn't say that bug is fixed because debug mode do not >generate mangle name, it simply rely on typeid to get it. Shouldn't >bug report be saying so ? Whatever, symbol generated by typeid can be >demangle by __cxa_demangle so it mustn't be that bad. I was trying to demangle the names with c++filt, which failed. Users should not have to write a C++ program using __cxa_demangle to read the output. If they are automatically demangled now then the bug is fixed.