Re: [cdt-debug-dev] CDI Variable framework [CDT 3.0.1]

["Mikhail Khodjaiants" <mikhailk@xxxxxxx>]

Baltasar,

Please, see my comments inline.

----- Original Message ----- 
From: "Belyavsky, Baltasar" <bbelyavsky@xxxxxx>
To: <cdt-debug-dev@xxxxxxxxxxx>
Sent: Friday, January 06, 2006 2:48 PM
Subject: [cdt-debug-dev] CDI Variable framework [CDT 3.0.1]


> Hi,
>
> I am implementing the Variable/Expression portions of the CDI framework
> (using CDT 3.0.1), and have two quick questions.
>
> Question 1:
> The local CDI variables are purposely never disposed (see the
> CVariable.dispose() method - there is a comment there stating that local
> variables should not be disposed...).  Is there a reason for this
> behaviour?

The assumption is the backend will destroy the local variables when the 
stack frame is destroyed. I don't remember what exactly was the problem - 
the person who implemented the CDI model for gdb is not available right now. 
I would suggest as a a temporary solution is to dispose the local varibales 
with the container stack frame in your implementation.

> Question 2:
> The following methods are never being called from anywhere in CDT:
>    1. ICDIType.getDetailTypeName()
>    2. ICDIExpressionManagement.getExpressions()
>    3. ICDIExpressionManagement.destroyExpressions()
>    4. ICDIExpressionManagement.destroyAllExpressions()
>
> Are there any plans for these methods in the future, or are they
> deprecated?

You can ignore these methods. The expression evaluation model has changed in 
the Eclipse Debug platform and these methods are remnants of the old model.
In general, the only existing implementation of the CDI API is based on gdb. 
The API will be revisited for the next major version according the feedback 
we are receiving from your group and from the Nokia/Freescale folks.

> Thanks,
> -
> Baltasar, Texas Instruments.