[cdt-dev] Local variables bug

[Don Howard <dhoward@xxxxxxxxxx>]

I'm looking into a cdt bug that I filed (28881).  An added comment (from
Mikhail K.) states that stack frames that contain variables with the same
name will map to one CDI variable object.

I don't understand what the CDI* members are in CStackFrame / CVariable /
CValue.


CStackFrame contains:

	CDIStackFrame (?)
	next frame
	associated thread
	list of CVariables (ok, so they are really CLocalVariables, but if
	you follow the inheritance back a bit you find that it's a
	CVariable)


CVariable contains: 

	parent (the associated CStackFrame?)
	CDIVariable (Haven't figured out what this is/represents)
	Value (this one seems obvious )


CValue contains:

	parent (the associated CValue?)
	value string 	 (seems obvious)
	CDIValue (Again, I'm missing the deeper meaning here)
	list of children (seems obvious - complex types)
	type code
	


What do the CID variables do/represent in these classes?  Is it a pointer
to something more concrete?  Or are these members there to allow
decoupling of some sort?





-- 
dhoward@xxxxxxxxxx
gdb engineering