#80 Incremental retrieval of variables in debugger

[Jan Ploski]

Up to and including version 0.6.0, EPIC retrieves values of ALL variables in a single request on each suspend event. This kills performance when working with complex data structures. Moreover, a single variable with a "large" value (e.g. several hundred kilobytes) is enough to make the debugger unusable. The format in which variables are exchanged between EPIC and Perl is quite cryptic, with the core module dumpvar_epic.pm being a hunk of uncommented code apparently borrowed from another project.

The goal of this feature request is to implement incremental (lazy) retrieval of variable values as they become requested by the user expanding items in the Variables view. By the way, the exchange format for variables should be specified and improved to be easier to extend and work with when debugging the EPIC debugger.

[Jan Ploski]

Logged In: YES
user_id=86907
Originator: YES

Significant parts implemented in CVS. Displaying of global variables and tracking of variable changes are temporarily disabled in CVS due to work in progress on this RFE.

[Jan Ploski]

Logged In: YES
user_id=86907
Originator: YES

Implemented in CVS. Displaying global variables now works again. Tracking of variable changes is still disabled.

[Jan Ploski]

Logged In: YES
user_id=86907
Originator: YES

Implemented in 0.6.1.