RE: [cdt-dev] Support for "read-sensitive" values

["Mikhail Khodjaiants" <Mikhail.Khodjaiants@xxxxxxx>]

Hi,

I agree, adding support for "read-sensitive" values is a useful feature.
Please, submit an enhancement request in Bugzilla.
 
> 1. Given a CVariable, what's the right way to notify the VariablesView
that this CVariable has changed and must be redisplayed?

The backend should fire an ICDIChangedEvent for the corresponding CDI
variable. 

> 2. I would like the context menu for read-sensitive values to have
"Fetch value" item right on the top. This menu is populated via
extensions > mechanism and I see no way to control the order. How do I
make a certain action appear on top?

I don't know how to control the appearance order, it's better to post
this question to the platform mailing list.

> 3. The variables view has a details pane, and the content of that
details pane is populated via MI's -data-evaluate-expression.  So, each
> expression will be evaluated twice -- first time to display it in the
tree, and second time to display it in details pane. Is it possible to
> make the details pane construct text based on variable objects used
for tree display, to eliminate this double evaluation?

The evaluation based on variable objects and on
"-data-evaluate-expression" in many cases provide two different
presentations for same variable. A good example is "char *". Of course,
this is specific for the gdb/mi implementation and can be changed if
needed for read-sensitive values.

Regards,
Mikhail

-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Vladimir Prus
Sent: 14 November 2006 19:20
To: CDT list.
Subject: [cdt-dev] Support for "read-sensitive" values


Hello!

I would like to extend the CDT debugger to support "read-sensitive"
values -- the values that cannot be read without altering the state of
the target system.

For example, expression *(int *)0x12345678 typically might be address of
a memory-mapped hardware register -- like some FIFO. Reading from that
address will extract the value from FIFO, so this not something that
should be done automatically on every step, but only by explicit request
from the programmer.

CDT has a mechanism to enable/disable variables, but it's not exactly
the same. Instead of enabling a "read-sensitive" value, I'd rather have
an explicit "read current value" command, that reads the value but does
not make the variable auto-update in future (like "enable" does).

I have a few technical questions:

1. Given a CVariable, what's the right way to notify the VariablesView
that this CVariable has changed and must be redisplayed?

2. I would like the context menu for read-sensitive values to have
"Fetch value" item right on the top. This menu is populated via
extensions mechanism and I see no way to control the order. How do I
make a certain action appear on top?

3. The variables view has a details pane, and the content of that
details pane is populated via MI's -data-evaluate-expression.  So, each
expression will be evaluated twice -- first time to display it in the
tree, and second time to display it in details pane. Is it possible to
make the details pane construct text based on variable objects used for
tree display, to eliminate this double evaluation?

Thanks in advance,
Volodya







_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

-- 
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium.  Thank you.