On Thu, 26 Jan 2006, David Berry wrote:
> Tim,
>
>> Just tried it out on an ADAM task (to see about leaks) and it's
>> essentially useless because on exit from the action the locator count
>> invariably goes up because the parameter system does not annul its
>> locators. So you simply find out that you got 3 new parameter locators
>> during the action...my enthusiasm is waning.
>
> Presumably this only happens on the first pass through the application (if
> you are running from orac-dr or from icl, etc). Once the parameters have
> been created the hds locator count should presumably settle down. Could
> you just skip the test on the first pass through the application?
>
I don't think that helps. Presumably if you run the app a second time with
a different mode it may well read in a parameter that did not get
requestred previously. I think it's a non-starter ...although that depends
on how much we care since clearly we could modify hdsInfoI so that it took
an extra argument that would be used to filter out locators we don't like.
ie
hdsInfoI( NULL, "LOCATORS", "EXTINCTION", &result, &status );
and this would return the number of open HDS locators that did not start
with the string "EXTINCTION." in their trace. This does of course require
us to know how ADAM stores it's parameters...(or maybe you want
"!EXTINCTION" for "not EXTINCTION"....). That might just work...
--
Tim Jenness
JAC software
http://www.jach.hawaii.edu/~timj
|