^running
(gdb)
~"0x7f7f0aec"
(gdb)
(gdb)
21.13 GDB/MI tracepoint commands
The tracepoint commands are not yet implemented.
21.14 GDB/MI variable objects
Motivation for variable objects in GDB/MI For the implementation of a variable debugger window (locals, watched expressions, and so on.), we are proposing the adaptation of the existing code used by Insight.
The two main reasons for that are:
1.It has been proven in practice (it is already on its second generation).
2.It will shorten development time (needless to say how important it is now).
The original interface was designed to be used by Tcl code, so it was slightly changed so it could be used through GDB/MI. This section describes the GDB/MI operations that will be available and gives some hints about their use.
NOTE: In addition to the set of operations described here, we expect the GUI implementation of a variable window to require, at least, the following operations:
•
•
•
•
Introduction to variable objects in GDB/MI The basic idea behind variable objects is the creation of a named object to represent a variable, an expression, a memory location or even a CPU register. For each object created, a set of operations is available for examining or changing its properties.
Furthermore, complex data types, such as C structures, are represented in a tree format. For instance, the struct type variable is the root and the children will represent the struct members. If a child is itself of a complex type, it will also have children of its own. Appropriate language differences are handled for C, C++ and Java.
When returning the actual values of the objects, this facility allows for the individual selection of the display format used in the result creation. It can be chosen among:
21.13 GDB/MI tracepoint commands 355