Appeal No. 2001-0653
Application 08/820,736
During execution of the profiled program in Profiler, routine
specific data is stored on stacks (p. 131) and after profiling is
completed, the "[Statistics|Save] command saves the statistics to
a .TFS (Turbo Profiler Statistics) file" (p. 113), which is a
profile data file having time and counter storage areas for each
area which was monitored. The arrangement or data structure of
the "procedure specific data storage area" is not claimed and
therefore does not distinguish over the storage in Profiler.
Profiler keeps track of statistics on each module of the
program and each area in each module and stores area specific
data in a .TFS file, where "[a]n area can be a single line, a
construct such as a loop, or an entire routine" (p. 12).
Profiler teaches that the areas to be profiled can be set using
the Add Areas menu for all routines (procedures) in all modules
of the program (p. 50): "Modules with Source adds area markers
for all routines in modules whose source code is available."
The collected statistics for the program can be viewed in the
Execution Profile window (pp. 13-14 & 55-56) by using the All
choice from the Filter command (p. 67) or the user can choose
only statistics for one module using the Module choice from the
Filter command (p. 68). In the examples of Figure 1.2 (p. 13),
Figure 1.4 (p. 15), and Figure 1.5 (p. 16), each line in the
Execution Profile window has four fields (pp. 13-14): (1) an area
name comprised of a module name (PRIME0) and an area name (31 for
- 11 -
Page: Previous 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 Next
Last modified: November 3, 2007