[GRASS5] Bug in r.mapcalc /r.null with NULLs

[Markus Neteler]

Hi all,

currently I am working with large dataset:
projection: 99 (Transverse Mercator)
zone:       0
north:      5776000
south:      5756000
west:       3558000
east:       3578000
nsres:      2.5
ewres:      2.5
rows:       8000
cols:       8000

I have imported a topo sheet and want to set ZERO to NULL.

 r.null dies in the middle,

 r.mapcalc dies, too, at 18%.
 +++ killed by SIGKILL +++

The call was:
r.mapcalc tk25_2="if(tk25=0,null(),tk25)"

I was expecting that GRASS works with such "large" datasets...
Does anyone have an idea where to search for the bug?

BTW: 
r.mapcalc tk25_2="if(tk25=0,2,tk25)"

runs o.k. So the bug must be in NULL stuff of GRASS library.

Thanks for any advice

 Markus

---------------------------------------- 
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo at geog.uni-hannover.de with
subject 'unsubscribe grass5'