From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20127 invoked by alias); 11 Jul 2005 13:21:14 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 19274 invoked by uid 22791); 11 Jul 2005 13:21:02 -0000 Received: from main.gmane.org (HELO ciao.gmane.org) (80.91.229.2) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 11 Jul 2005 13:21:02 +0000 Received: from root by ciao.gmane.org with local (Exim 4.43) id 1DryCm-00072L-QD for gdb@sources.redhat.com; Mon, 11 Jul 2005 15:20:16 +0200 Received: from zigzag.lvk.cs.msu.su ([158.250.17.23]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 11 Jul 2005 15:20:16 +0200 Received: from ghost by zigzag.lvk.cs.msu.su with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 11 Jul 2005 15:20:16 +0200 To: gdb@sources.redhat.com From: Vladimir Prus Subject: Re: Formatting of function pointer value Date: Mon, 11 Jul 2005 13:21:00 -0000 Message-ID: References: <20050708135810.GB17089@nevyn.them.org> <17106.5796.850869.491390@farnswood.snap.net.nz> <20050711130742.GB25755@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit User-Agent: KNode/0.8.2 X-SW-Source: 2005-07/txt/msg00111.txt.bz2 Daniel Jacobowitz wrote: >> To clarify more, here's what I get with MI: >> >> -data-evaluate-expression *p3 >> ^done,value="{int (int)} 0xb7ee6e9c <__DTOR_END__+4>" >> (gdb) >> -var-create VP3 0 *p3 >> ^done,name="VP3",numchild="0",type="int (int)" >> (gdb) >> -var-evaluate-expression VP3 >> ^done,value="{int (int)} 0xb7ee6e9c <__DTOR_END__+4>" >> >> The type enclosed in {} is still there. > > The intention is that this is a user-readable value, to be displayed. Hmm.. since MI is for gdb frontends, this just imposes work for frontend. It frontend wants to display the type, it can get this information easily with extra MI command, while stripping '{}' is somewhat hacky. Especially because {} is also used to delimit arrays. > There's limited facility for computing values with machine-readable > results, probably because there has been limited need for it to date. So, 1. It's not possible to avoid those {} in the current code, using MI or CLI. 2. It's not likely that this will change Right? If so, then I'll just drop the ball, and use a hacky {}-stripping code in kdevelop. - Volodya