[Carpet] memory allocation in global loop-local mode?

[Bela Szilagyi]

In one of my thorns (taken after AHFinderDirect's mask-setter routine schedule 
bing) I had


schedule my_routine in my_group
        {
        lang: C
       storage: my_var
        options: global loop-local
        } "..."


while the parfile says

Carpet::enable_all_storage = no

The routine ended up being called, at least once within the first course 
time-step worth of time, with my_var being set to NULL.

A bit of peaking into it with gdb has shown that not all calls to the routine 
were lacking the memory, but, in the one case this variable would have been 
used, the memory was not there.

Is this a bug or a feature? In other terms -- does "global loop-local" imply 
that one should not assume memory associated with tmp_var ?


-- 
Bela Szilagyi

Max-Planck-Institut für Gravitationsphysik
Albert-Einstein-Institut
Tel: +49 331 567 7632
Fax: +49 331 567 7649