Initial support for VDB python-based variable objects
Due to a limitation of GDB itself, one cannot create variable
object for "synthetic" argument/local created by custom frame
decorator. Therefore one cannot "dig deeper" and inspect contents
of such a variable in case it is a kind of composite - like an
object on a heap referring to another objects.
This is a problem when a debugee is does not have debug information
and / or it's language is not C - such as when debugging JITed code.
This (experimental) commit adds a parallel implementation of variable
objects done completely in python. This new varobj MI interface is a
super-set of GDB's builtin varobj MI interface.
# generated from project definition
# load package dependencies
load 'package.deps.rake'
# kludge: clear some invalid dependencies of libwidg
# (should be fixed in baseline)
clear "stx:libwidg" => "stx:libui"
clear "stx:libwidg2" => "stx:libui"
project :'vdb.do:baseline' do
# preamble
# --------
package "stx:libbasic"
package "stx:goodies/announcements"
package "stx:goodies/regex"
package "stx:libbasic2"
package "stx:libcomp"
package "stx:goodies/refactoryBrowser/parser"
package "stx:libbasic3"
package "stx:libview"
package "stx:libui"
package "stx:libview2"
package "stx:libwidg"
package "stx:goodies/magritte"
package "stx:libhtml"
package "stx:libwidg2"
package "stx:libtool"
package "jv:libgdbs"
package "stx:goodies/communication"
package "stx:libtool2"
package "stx:libcompat"
package "stx:goodies/xml/vw"
package "jv:vdb"
application "jv:vdb/application"
# postamble
# ---------
end