[GRASS-dev] [GRASS GIS] #2351: g.version segfaults when the build is not perfect

[GRASS GIS]

#2351: g.version segfaults when the build is not perfect
----------------------------------------------------------+-----------------
 Reporter:  wenzeslaus                                    |       Owner:  grass-dev@…              
     Type:  defect                                        |      Status:  new                      
 Priority:  normal                                        |   Milestone:  7.0.0                    
Component:  Compiling                                     |     Version:  unspecified              
 Keywords:  GIS_H_VERSION, GIS_H_DATA, libgis, g.version  |    Platform:  Linux                    
      Cpu:  Unspecified                                   |  
----------------------------------------------------------+-----------------

Comment(by wenzeslaus):

 Replying to [comment:1 neteler]:
 > Replying to [ticket:2351 wenzeslaus]:
 > > G7:g.version often fails, segfaults in particular, with some wrong
 builds.
 > ...
 > > {{{
 > > > g.gisenv set=DEBUG=5
 > > bash: /usr/lib/grass70/etc/prompt.py: File o directory non esistente
 > ...
 > > }}}
 >
 > The fact that etc/prompt.py indicates that the grass70 start script is
 > outdated with respect to the SVN version. So, the "make install" has not
 been
 > properly performed or the "grass70" script in the path is an old version
 > (e.g old copy rather a link when using a non-installed compiled version
 from
 > the source tree). Check that start script first.

 I'm not sure if I fully understand what you are saying. Anyway, in this
 GRASS was [http://lists.osgeo.org/pipermail/grass-
 user/2014-June/070480.html installed from packages] and the error message
 says that there is no `promp.py` file. This indeed seems like a broken
 build or installation, however `g.version` was failing even in the other
 case where this error was not reported and the point is to make
 `g.version` resistant to errors and strange configurations since it is
 often used within environments like this (for example it wouldn't be a
 good idea to write `g.version` in Python).

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