Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: jacques <jacqueslenormand@sympatico.ca>
Cc: gdb@sources.redhat.com
Subject: Machine interface
Date: Tue, 19 Aug 2003 06:45:00 -0000	[thread overview]
Message-ID: <3F417228.1010109@sympatico.ca> (raw)
In-Reply-To: <20030818193344.GA21937@nevyn.them.org>

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<int,std::allocator<int> >> = 
{<_Vector_alloc_base<int,std::allocator<int>,true>> = {_M_start = 
0x804aa50, _M_finish = 0x804aa58, _M_end_of_storage = 0x804aa58}, <No 
data fields>}, <No data fields>}"

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





  reply	other threads:[~2003-08-19  6:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-03 22:09 Amusing problem in current libthread_db Daniel Jacobowitz
2003-06-03 22:30 ` Roland McGrath
2003-08-18 19:33   ` Daniel Jacobowitz
2003-08-19  6:45     ` jacques [this message]
2003-08-19 13:30       ` Machine interface Andrew Cagney
2003-08-19 14:00         ` Alain Magloire
2003-08-25  8:17     ` Amusing problem in current libthread_db Ulrich Drepper
2005-03-18 16:01 Machine interface Greg Law
2005-03-18 16:05 ` Bob Rossi
2005-03-18 16:11   ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3F417228.1010109@sympatico.ca \
    --to=jacqueslenormand@sympatico.ca \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox