Changes between Version 8 and Version 9 of DebuggingMapserver
- Timestamp:
- Feb 3, 2009, 7:28:21 AM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DebuggingMapserver
v8 v9 4 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. See [http://www.mapserver.org/development/rfc/ms-rfc-28.html RFC28] for more info. 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 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.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. 7 7 5. For issues with !PerlMapScript see: [wiki:PerlMapScriptDebugging] 8 8 6. Double Check the EXTENT values in the mapfile against the known extent of the data being used.