[GRASS-dev] Re: [GRASS GIS] #735: r.in.wms causes g.parser buffer
owerflow
GRASS GIS
trac at osgeo.org
Tue Aug 25 15:08:12 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 glynn):
Replying to [ticket:735 marisn]:
> I used r.in.wms to download high resolution topographical maps from
local WMS service. Download part went just fine but it resulted into 287
tiles. Then r.in.wms calls r.in.gdalwarp
input=/home/maris/grassdata/wms_download/topo_10k_psrs_0.png and so on 287
tile names. Such call results in buffer owerflow in g.parser:
I can fix the buffer overflow by using G_asprintf(), but some operating
systems aren't going to like storing that much data in an environment
variable (Linux 2.6 doesn't mind, but a limit of 4K for argv+environ is
quite common).
The Python scripting library in GRASS 7 has g.parser write the information
to stdout rather than using environment variables, so this isn't an issue
there.
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/735#comment:1>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list