Ticket #221 (closed defect: fixed)

Opened 11 years ago

Last modified 11 years ago

[GDAL] Use of msBuildPath() with GDALGetDescription()???

Reported by: dmorissette Owned by: warmerdam
Priority: high Milestone:
Component: GDAL Support Version: 4.0
Severity: normal Keywords:
Cc:

Description 

I noticed in mapraster.c that calls to GDALReadWorldFile() use calls to 
msBuildPath() combined with GDALGetDescription().  

Is GDALGetDescription() supposed to return the full path that was previously 
passed to GDALOpen()?  If it does then those msBuildPath() calls are not 
necessary since msBuildPath() has been called already for GDALOpen().
If it doesn't then we need to know what the function returns exactly.

Frank, can you please confirm that it is safe to use GDALGetDescription() the 
way it is used in mapraster.c?

Change History

Changed 11 years ago by dmorissette

  • cc lacroix@… added 
Note that there is also a potential problem with the recursive calls to 
msBuildPath() combined with GDALetDescription() but this is covered by bug 220.

Changed 11 years ago by fwarmerdam

  • status changed from new to closed
  • resolution set to fixed 
Daniel, 

You are right ... the path will already be extended in what is returned by
GDALGetDescription().  I have removed the msBuildPath() calls for that
one spot in mapraster.c.
Note: See TracTickets for help on using tickets.