From: Joel Brobecker <brobecker@adacore.com>
To: Rob Quill <rob.quill@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Tests for expressions
Date: Sun, 04 Nov 2007 17:35:00 -0000 [thread overview]
Message-ID: <20071104173506.GA6729@adacore.com> (raw)
In-Reply-To: <baf6008d0711040930r170a0fbem25aef89b04200e16@mail.gmail.com>
> I was wondering if anyone knew of a test in the test suite which tests
> GDB's evaluation of expressions. I am trying to understand all of the
> cases for the switch statement in the switch statement in
> evaluate_subexp_standard in ./gdb/eval.c and thought that looking at
> how the testsuite uses them would be a good place to start.
Any "print" command will use the expression evaluation routine.
I find it harder to understand the evaluation routine without having
a look at expression.h (for the expression "tree"), and the associated
parsing routine. See c-exp.y, that shows how the expression tree is
built, will show you what data is where in each node depending on the
node kind.
--
Joel
prev parent reply other threads:[~2007-11-04 17:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-04 17:30 Rob Quill
2007-11-04 17:35 ` Joel Brobecker [this message]
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=20071104173506.GA6729@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=rob.quill@gmail.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