[GRASS-dev] g.copy segfaulting in 6.3 snapshot 20070922

[Volker Wichmann]

It would be certainly nice to know why, if you like to dig deeper have a 
look at thread [GRASS-dev] [grass-code I][431] g.copy segmentation fault 
( http://www.mail-archive.com/grass-dev@grass.itc.it/msg00359.html )

Volker

Maris Nartiss wrote:

>It may be not a GRASS issue, but it would be nice to know why it
>happens, as, probably, there are some tricks to disable THIS
>optimization in GRASS. Like adding some *magic* in code or tests in
>autoconf part to disable optimization if system is FOO.
>
>Just 0.002$,
>Maris.
>
>2007/9/27, Volker Wichmann <wichmann at laserdata.at>:
>  
>
>>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
>>    
>>