This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [PATCH] Add support for tracking/evaluating dwarf2 location expressions
- To: Jim Blandy <jimb at cygnus dot com>, Daniel Berlin <dberlin at redhat dot com>
- Subject: Re: [PATCH] Add support for tracking/evaluating dwarf2 location expressions
- From: Andrew Cagney <ac131313 at cygnus dot com>
- Date: Wed, 06 Jun 2001 11:35:40 -0400
- Cc: gdb-patches at sources dot redhat dot com
- References: <Pine.LNX.4.33.0103301400270.24037-100000@www.cgsoftware.com> <nppud28jdl.fsf@zwingli.cygnus.com>
Two things:
GDB has, well almost has, a byte code interpreter it 100% controls. Jim,
remember tracepoints?
To initially set the bar very high (I'm sure it will soon come crashing
down) the byte code interpreter should to be implemented as a true state
machine. This is significant - instead of assuming that target_read()
returns the data immediatly, it should instead be designed to allow for
the day when target_read() returns ERETRY.
Hmm, no, I lied, three things :-)
To follow up Jim's comment about GDB 100% controlling the byte code
interpreter. Am I correct to think that, for tracepoints to continue
working, GDB will need to translate DWARF2 bytecode expressions into
tracepoint expressions so that they can be run on the target when
fetching variables?
Andrew