[postgis-tickets] [PostGIS] #2287: --enable-debug builds are way too verbose

[PostGIS]

#2287: --enable-debug builds are way too verbose
----------------------+-----------------------------------------------------
 Reporter:  alvherre  |       Owner:  pramsey
     Type:  defect    |      Status:  new    
 Priority:  medium    |   Milestone:         
Component:  postgis   |     Version:  trunk  
 Keywords:            |  
----------------------+-----------------------------------------------------
 We were debugging a crash on a customer (which turned out to be stack
 overflow in libgeos, apparently fixed in geos revs 3711 and 3751) and
 noticed that when running with --enable-debug enabled, there are some
 macros which cause too much output: the debug messages are emitted at
 level NOTICE, so it's fairly difficult to silence them.  This has been
 mentioned in the mailing list as causing problems for the regression
 tests: http://lists.osgeo.org/pipermail/postgis-
 devel/2010-February/008742.html

 It seems to me that it'd be more useful to emit the messages in DEBUGx
 level instead of NOTICE, where the "x" depends on the verbosity specified
 by the debugging call itself; so for example a POSTGIS_DEBUG(1) call would
 be emitted as DEBUG1 and so on.

 One (simple to resolve) problem is that there are several such macros.
 Not only there's POSTGIS_DEBUG, but there's also RASTER_DEBUG and
 POSTGIS_RT_DEBUG, and their "..F" counterparts.  Probably, they should all
 be tweaked in much the same way.  But there's one that's a bit more
 problematic --- LW_DEBUG.  That one calls lwnotice() instead, which is a
 configurable notice printer.

 Is there a consensus on how to deal with this?  With some guidance, I can
 try to address the problem and propose a patch.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/2287>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.