From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19510 invoked by alias); 29 Apr 2011 13:15:06 -0000 Received: (qmail 19502 invoked by uid 22791); 29 Apr 2011 13:15:05 -0000 X-SWARE-Spam-Status: No, hits=-6.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD 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; Fri, 29 Apr 2011 13:14:50 +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 p3TDEn5n009710 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 29 Apr 2011 09:14:49 -0400 Received: from host1.jankratochvil.net (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p3TDElRu017669 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 29 Apr 2011 09:14:49 -0400 Received: from host1.jankratochvil.net (localhost [127.0.0.1]) by host1.jankratochvil.net (8.14.4/8.14.4) with ESMTP id p3TDElY6025945; Fri, 29 Apr 2011 15:14:47 +0200 Received: (from jkratoch@localhost) by host1.jankratochvil.net (8.14.4/8.14.4/Submit) id p3TDEkFM025944; Fri, 29 Apr 2011 15:14:46 +0200 Date: Fri, 29 Apr 2011 13:15:00 -0000 From: Jan Kratochvil To: Brian Budge Cc: gdb@sourceware.org Subject: Re: can't step into, or print variables inside of C++ template function Message-ID: <20110429131446.GA25816@host1.jankratochvil.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) 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: 2011-04/txt/msg00166.txt.bz2 On Wed, 27 Apr 2011 18:43:16 +0200, Brian Budge wrote: > A quick update: This works under gcc 4.4. Unsure if a bug should be > filed against gdb to work with newer debug information, or against gcc > for breaking the debug information. Sometimes it is GCC bug, sometimes GDB bug. But the GCC or GDB maintainers will reassign it appropriately when needed. It is more important to file a reproducer, I cannot say anything more about it. Both GCC and GDB have heavy regression testsuites and apparently this case is not yet covered there. Thanks, Jan