[GRASS-dev] Re: [GRASS GIS] #1032: ErrorCommandExecution g.proj

[GRASS GIS]

#1032: ErrorCommandExecution g.proj
----------------------+-----------------------------------------------------
 Reporter:  sallar    |       Owner:  grass-dev@…              
     Type:  defect    |      Status:  new                      
 Priority:  critical  |   Milestone:  6.4.0                    
Component:  default   |     Version:  6.4.0 RCs                
 Keywords:  g.proj    |    Platform:  Linux                    
      Cpu:  x86-32    |  
----------------------+-----------------------------------------------------
Changes (by martinl):

  * priority:  blocker => critical


Comment:

 Replying to [comment:16 martinl]:
 > > > I'm not sure why the backtrace stopped (maybe the caller was built
 with -fomit-frame-pointer?), but it looks like heap corruption. In which
 case, the stack trace doesn't really help, as the error is in whatever
 caused the heap corruption, not whatever happens to get bitten by it.
 > > > valgrind might be able to help here.
 > >
 > > Can you post here valgrind output ?
 > >
 > > http://grass.osgeo.org/wiki/GRASS_Debugging#Using_Valgrind
 >
 > The ticket is marked as "blocker", valgrind output could help to solved
 this issue.

 downgrading the priority...

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/1032#comment:17>
GRASS GIS <http://grass.osgeo.org>