[GRASS-dev] Re: [GRASS GIS] #735: r.in.wms causes g.parser buffer owerflow

GRASS GIS trac at osgeo.org
Thu Aug 27 10:08:24 EDT 2009


#735: r.in.wms causes g.parser buffer owerflow
---------------------+------------------------------------------------------
  Reporter:  marisn  |       Owner:  grass-dev at lists.osgeo.org
      Type:  defect  |      Status:  new                      
  Priority:  normal  |   Milestone:  6.5.0                    
 Component:  Raster  |     Version:  svn-develbranch6         
Resolution:          |    Keywords:                           
  Platform:  Linux   |         Cpu:  Unspecified              
---------------------+------------------------------------------------------
Comment (by marisn):

 Replying to [comment:2 hamish]:
 > from grass65/scripts/r.in.wms/wms.request:
 >
 > {{{
 >   g.message "Requesting ${NUMBER_OF_TILES} tiles."
 > }}}
 g.message is a bad choice, as on fast machine with fast WMS server it too
 soon gets burried in >200 tile downloading messages.

 Glynn: no idea. It's too hardcore for me. Still IMHO buffer owerflow isn't
 the right way how to deal with error conditions.

 It would be nice if r.in.wms could calculate resulting arg length and fail
 if it exceeds systems capabilities (theoretical limits).

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/735#comment:4>
GRASS GIS <http://grass.osgeo.org>


More information about the grass-dev mailing list