[PerfSuite-bugs] psprocess -c bug in 0.6.2a3

[Rick K. <rk...@nc...>]

Henry,

Thanks very much for testing this out and reporting the problem.  You 
located the problem spot perfectly and yes, unfortunately it is a bug in 
psprocess.  I'm going to copy the list on this in case others run across 
the same issue and will package an a4 release to fix this problem as soon 
as possible.  The combine operation is very common for people to use so
this shouldn't stay unaddressed for long. Fortunately, there is a quick
fix that can be applied to combine.tcl either before or after
installation.  At the beginning of the source code in combine.tcl,
lines 56-60 are:

   proc readAndValidateMultiple {fileList ignoreErrors} {
       global timers

       set res {}
       set doctype ""

The following line should be added after line 60 ("set doctype"):

       set timers(total,domparse) 0

Within the distribution, combine.tcl can be found in the directory:

   src/tools/psprocess/tcl

After installation, it will be located in:

   $PREFIX/share/perfsuite/tclbin/psprocess

This is a bug that was introduced with a new capability of this release 
(measuring the time necessary to do XML document processing).

Sorry I missed this before the release!  But thanks again for the report 
and also the very good news that things appear to work otherwise on 
Columbia.

Rick


On Wed, 3 May 2006, Haoqiang H. Jin wrote:

> Hi Rick,
>
> Glad to see you had the new version released.  I installed
> this version on our Columbia system.  Except for a minor
> problem, it worked pretty much out of the box.  The minor
> glitch occurred when I tried psprocess in the combined mode.
>
> % psprocess -c a.out.0.m.xml a.out.1.m.xml
> can't read "timers(total,domparse)": no such variable
>
> The error seems to be generated from 'combine.tcl'
> in line 78:
>        incr timers(total,domparse) [expr {$stoptime - $starttime}]
>
> If I comment out this line or replace 'incr' with 'set',
> psprocess ran successfully.  Is this a bug or something
> else that I should specify in the command line?
>
> Thanks for your great work to make the package available!
>
> -Henry