Changes between Version 5 and Version 6 of DebuggingMapserver
- Timestamp:
- Jan 27, 2009, 1:25:27 PM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DebuggingMapserver
v5 v6 2 2 3 3 1. Use [http://www.mapserver.org/utilities/shp2img.html shp2img] from the commandline to test your map file if possible. It is often much easier to debug problems without the extra complications of the web environment. 4 2. Turn on debugging. As of !MapServer 3.7 the MAP, LAYER and CLASS objects have a DEBUG keyword. If you include a DEBUG keyword in objects giving problems following by a greater than zero number, then various debugging output about the map, layer or class may be generated. The quality and quantity of debugging output varies widely. Note: Using MS4.0.1 I discovered that the correct syntax for DEBUG is simply DEBUG ON/OFF. Attempting to use DEBUG 5, etc. in a map file results in addtional bugs. Very confusing.4 2. Turn on debugging. As of !MapServer 5.0 the [http://www.mapserver.org/mapfile/map.html MAP], and [http://www.mapserver.org/mapfile/layer.html LAYER] objects have a DEBUG keyword. If you include a DEBUG keyword in objects giving problems following by a greater than zero number, then various debugging output about the map, layer or class may be generated. 5 5 3. Some additional debugging can be turned on from GDAL and OGR by setting the CPL_DEBUG environment variable to on. Similarly additional PROJ.4 debug info can be produced by setting PROJ_DEBUG to ON. 6 6 4. The MS_ERRORFILE environment variable can be set to a path (or "stdout" or "stderr") to have all errors handled within MapServer to a logfile or console. This can be helpful, especially for situations where the error is otherwise ignored, or doesn't get all the way back to the client.