trident-job / delphi-code-coverage

Automatically exported from code.google.com/p/delphi-code-coverage
0 stars 0 forks source link

Support "Dead Memory" output #34

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Launch tool
2. Configure tool ( with wizard ... )
3. Run Coverage...

What is the expected output? What do you see instead?

Ability to have seperate tehncial output about "dead memory" areas. The "dead 
memory" would stand for all the occupied memory bu variables, constants and 
other data structures, that are not:

 - freed ( label "F" )
 - used anywhere in the code ( label "U" )
 - initialized ( labeled "I" )

What version of the product are you using? On what operating system?

RC1

Please provide any additional information below.

To add this feature, the following TODO could be used:

1. On each statement ( <if..then..[begin..end]> ; <for..to..do..[begin..end]> ; 
<repeat..unti> ; and others... ) record used variables into data structure;
2. After code is scanned / covered, perform static code scan and compare if the 
variables used ihn these statements mentioned above exposes the same variables 
declared in the unit / project. If not, provide new column in output labeled 
"Dead Memory", which would describe the main issue that memory is not anymore 
fully accessible for the program...
3. scan the code and combine the found issues in the form of array, that would 
make a columns fiel look like "F,U,I", saying, that the scanned code / 
statement block has got unfreed memory, uninitialized variables and also 
variables are unused ( declared but no value assigned ).

Original issue reported on code.google.com by linards....@gmail.com on 8 Apr 2012 at 3:03

GoogleCodeExporter commented 9 years ago

Original comment by e.kotlya...@gmail.com on 16 Oct 2012 at 4:12