From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26652 invoked by alias); 19 Aug 2003 06:45:42 -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 26642 invoked from network); 19 Aug 2003 06:45:38 -0000 Received: from unknown (HELO tomts19-srv.bellnexxia.net) (209.226.175.73) by sources.redhat.com with SMTP; 19 Aug 2003 06:45:38 -0000 Received: from sympatico.ca ([65.94.38.219]) by tomts19-srv.bellnexxia.net (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP id <20030819064537.OACB19334.tomts19-srv.bellnexxia.net@sympatico.ca> for ; Tue, 19 Aug 2003 02:45:37 -0400 Message-ID: <3F417228.1010109@sympatico.ca> Date: Tue, 19 Aug 2003 06:45:00 -0000 From: jacques User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030714 Debian/1.4-2 X-Accept-Language: en MIME-Version: 1.0 CC: gdb@sources.redhat.com Subject: Machine interface References: <20030603220912.GA7922@nevyn.them.org> <200306032230.h53MUlA22339@magilla.sf.frob.com> <20030818193344.GA21937@nevyn.them.org> In-Reply-To: <20030818193344.GA21937@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-08/txt/msg00208.txt.bz2 Hello, I've been doing some MI interface testing, and am in need of some grammar clarifications. After running until a breakpoint, I do the following: (gdb) -data-evaluate-expression b ^done,value="{<_Vector_base >> = {<_Vector_alloc_base,true>> = {_M_start = 0x804aa50, _M_finish = 0x804aa58, _M_end_of_storage = 0x804aa58}, }, }" Which is of the format: output => result-record => "^" result-class ( "," result ) result-class => "done" result => variable "=" value value => tuple tuple => "{" result "}" ... Now all is well and fine, however the meat of the output, being the variable and value nonterminal symbols are unparseable! Indeed, they are composed of: variable => string value => const => c-string (since I can't fanthom not running into a const value after a while) In this case, <_Vector_base<....>> is unparseable, and I wouldn't be able to know how to handle all cases. Furthermore, I don't see the distinction between c-string and string. I see how the production would depend on the programming language being being debugged, but it seems quite important to me. --Jacques