We did a lot of tests back then, and it seems to be a problem with the
compiler optimisation code. This issue isn't fixed, but you can work
around it by re-compiling g.copy without optimisation enabled (see
thread below). I don't think it is a GRASS issue.
Volker
Francesco P. Lovergine wrote:
On Thu, Sep 27, 2007 at 05:49:01PM +0300, Maris Nartiss wrote:
there where problems with g.copy some time a go, but problem went away
without explanation about it's source/roots.
http://wald.intevation.org/tracker/?group_id=21&atid=204&func=detail&aid=431
It happens with any raster from the spearfish60 dataset, on Debian GNU/Linux.
If you had problem to reproduce it I can track better the issue in a
debugging session.
_______________________________________________
grass-dev mailing list
[email protected]
http://grass.itc.it/mailman/listinfo/grass-dev
