[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 glynn):

 Replying to [comment:2 wenzeslaus]:

 > > 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.

 lib/init/grass.py used to write "PROMPT_COMMAND=<gisbase>/etc/prompt.py"
 into the local .bashrc file which it generates. r60216 removed the
 prompt.py script and instead defines a bash function to generate the
 prompt.

 The error message suggests that only part of r60216 is in effect;
 specifically, prompt.py has been removed but PROMPT_COMMAND still refers
 to it. This could be caused by the local .bashrc not being generated at
 startup and an old version left over from a previous session being used
 instead.

 > This indeed seems like a broken build or installation, however
 `g.version` was failing even in the other case
 The prompt.py error may well be unrelated to the problems with g.version.
 However, it suggests problems with the build or installation, and
 g.version is sensitive to the build and installation.

 The problem appears to arise from a combination of two issues: g.version
 not being robust against bad input data, and g.version getting bad input
 data. The prompt.py issue hints at a possible reason for the latter.

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