[GRASS-dev] [GRASS GIS] #1906: Raster "title" longer than 100 characters segfaults ps.map -- Request to extend the field's capacity.

[GRASS GIS]

#1906: Raster "title" longer than 100 characters segfaults ps.map -- Request to
extend the field's capacity.
----------------------------------------------+-----------------------------
 Reporter:  nikosa                            |       Owner:  grass-dev@…              
     Type:  enhancement                       |      Status:  new                      
 Priority:  minor                             |   Milestone:  7.0.0                    
Component:  Ps.map                            |     Version:  svn-trunk                
 Keywords:  ps.map, header, r.support, title  |    Platform:  Unspecified              
      Cpu:  x86-64                            |  
----------------------------------------------+-----------------------------

Comment(by nikosa):

 Replying to [comment:1 neteler]:
 > There seems to be a (wild) mixture of buffer lengths for the raster map
 title:[[BR]]
 > Compare:[[BR]]
 > * http://grass.osgeo.org/programming7/put__title_8c_source.html#l00016
 >   int Rast_put_cell_title()[[BR]]
 > * raster/r.support/main.c: #define MAX_TITLE_LEN 1022[[BR]]
 > * r.clump/main.c:    char title[512];[[BR]]
 > * r.los/main.c:    char title[128];[[BR]]
 > * r.neighbors/main.c:    char title[1024];[[BR]]
 > * r.param.scale/close_down.c:    char map_title[80], map_type[32];[[BR]]
 > * etc[[BR]]
 > * ps.map/ps_info.h:    char celltitle[100];[[BR]]

 Interesting mixture :-). If it is not possible to ''equalise'' all these,
 maybe, at the very least, warn the user to "conform" to a fixed length and
 below, and not letting him to a scary seg-fault?

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