debug and Mapserver crash

Stephen Woodbridge woodbri at SWOODBRIDGE.COM
Mon Mar 14 08:53:28 EST 2005


I'm not sure what happens on a crash, but my experience with the DEBUG
and LOG are as follows.

1) If LOG is turned on it only writes one line to the logfile that I did
not find to be very useful for anything.

2) DEBUG output does NOT go to the LOG file it goes to STDERR which
should put it into the apache/error_log. I opened a separate window and
did a "tail -f /var/log/apache/error_log". FWIW, the only information
written during DEBUG is layer timing stats. so if the files are flushed
on a crash, you might get a clue about what layer it crashed on.

While this is better than nothing, I would be nice if the DEBUG took a
LEVEL which controlled the level of verbosity of the output as a bit
mask or level like:

DEBUG  1  - timing stats
DEBUG  2  - subroutine
DEBUG  4  - file/connection OPEN/CLOSE
DEBUG  8  - SQL statements
DEBUG 16  - etc

But alas, it doesn't work that way.

   -Steve W.

Bart van den Eijnden wrote:
> Hi list,
> does Mapserver write debug info for the functions that are successfully
> called before a crash (Internal Server Error) occurs?
> Or when it crashes it won't write anything at all?
> Best regards,
> Bart
> --
> Using Opera's revolutionary e-mail client:

More information about the mapserver-dev mailing list