[GRASS-dev] Re: [GRASS GIS] #50: g.copy segfaults (debian.gfoss.it package) [and latest SVN]

[GRASS GIS]

#50: g.copy segfaults (debian.gfoss.it package) [and latest SVN]
----------------------+-----------------------------------------------------
  Reporter:  steko    |       Owner:  grass-dev at lists.osgeo.org
      Type:  defect   |      Status:  new                      
  Priority:  major    |   Milestone:  6.4.0                    
 Component:  default  |     Version:  6.3.0 RCs                
Resolution:           |    Keywords:  g.copy                   
----------------------+-----------------------------------------------------
Comment (by marisn):

 Hunting down this bug is not as easy. I once spent some days trying but
 without luck.(1)[[BR]]
 I enabled/disabled all -O1 flags one-by-one, but none of optimisation
 flags cause segfault. It must be combination of them;(1) [[BR]]
 Using valgrind on optimised code is not usefull;(1)[[BR]]
 Changing G_lstat() with lstat() in general/manage/lib/do_copy.c fixes
 problem;(1)[[BR]]
 Currently all segfault reporters where using GCC 4.x. I have not tested
 grass_trunk for some time on this bug, but when it was first reported, I
 was able to reproduce segfault on two 32bit Gentoo systems with GCC-4.x
 without stack protection. Glynn - try to disable stack protection before
 running g.copy. Also please explain how to get proper asm backtrace or any
 other variables You are interested into to add printf's, as when I used
 printf's, I was not able to spot any strange values.

 1.
 http://wald.intevation.org/tracker/index.php?func=detail&aid=431&group_id=21&atid=204

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/50#comment:8>
GRASS GIS <http://grass.osgeo.org>
GRASS Geographic Information System (GRASS GIS) - http://grass.osgeo.org/