From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19299 invoked by alias); 12 Aug 2008 14:40:28 -0000 Received: (qmail 19282 invoked by uid 22791); 12 Aug 2008 14:40:27 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 12 Aug 2008 14:39:48 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 92CE798100; Tue, 12 Aug 2008 14:39:46 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 6DC0198015; Tue, 12 Aug 2008 14:39:46 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1KSv2H-0001MD-Kl; Tue, 12 Aug 2008 10:39:45 -0400 Date: Tue, 12 Aug 2008 16:12:00 -0000 From: Daniel Jacobowitz To: =?iso-8859-1?Q?Andr=E9_P=F6nitz?= Cc: gdb@sourceware.org Subject: Re: problem with gdb's 'call' Message-ID: <20080812143945.GA5050@caradoc.them.org> Mail-Followup-To: =?iso-8859-1?Q?Andr=E9_P=F6nitz?= , gdb@sourceware.org References: <200808121636.43694.apoenitz@trolltech.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <200808121636.43694.apoenitz@trolltech.com> User-Agent: Mutt/1.5.17 (2008-05-11) 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: 2008-08/txt/msg00162.txt.bz2 On Tue, Aug 12, 2008 at 04:36:40PM +0200, André Pönitz wrote: > (gdb) p _Z3fooIiET_v > $1 = {int (void)} 0x400544 ()> > > (gdb) call _Z3fooIiET_v() > /build/buildd/gdb-6.8/gdb/valops.c:2069: internal-error: find_oload_champ_namespace_loop: > Assertion `new_oload_champ != -1' failed. > A problem internal to GDB has been detected, I've seen this error recently, with pointers to members. I don't think my patches will fix this particular case (the OP_VAR_VALUE rather than STRUCTOP_MPTR case). > I already use the mangled name of the symbol as I did not find a way to > quote 'call foo()' in a way that looks acceptable to gdb. It's because of the templated return type. The quoting that works today is (gross, I know): p 'int foo'() But it doesn't help, there's the same error. > Is there a way to make the gdb core accept the mangled name without > attempting to demangling it (to avoid the crash)? The crash has nothing to do with demangling, but you can disable overload resolution and that should help. "set overload-resolution off". Or just fix the bug :-) -- Daniel Jacobowitz CodeSourcery