Debug info?

[Luke Kenneth Casson Leighton]

the same thing is done in freedce.

the macros are, except for an extra argument (specifying
the 'class' by enum), functionally and completely identical,
including having to have the extra brackets around the
printf-style args.

you can run a server and enable a whole class of debug
messages: freedce lists about 48 such classes.

luke


On Thu, Aug 23, 2001 at 06:10:34PM +0200, Elrond wrote:
> On Wed, Aug 22, 2001 at 01:09:29PM -0500, Peter Samuelson wrote:
> > 
> > [Elrond]
> > > -d is somehow broken... no real idea why, but it's broken.
> > > (and I don't feel like fixing it)
> > 
> > The whole debug system is a convoluted mess, IMO.  I tried to clean it
> > up awhile back and only managed to confuse myself.  In fact, separating
> > out my debug "cleanups" from my pathname work is the main reason the
> > latter hasn't been committed yet.
> 
> head has rewritten the debug-stuff to some degree... they
> added debug-classes (like sendmail), so that you have
> different classes with loglevels and the like.
> 
> I actualy like the idea.
> 
> I haven't even tried to merge this over, because I knew,
> you were working near the debug stuff, and I didn't want to
> cause conflicts in bigger parts of the code.
> 
> 
> > I may revisit my debug code work after the pathname stuff is in and
> > working....
> 
> You could try to commit some of the small stuff in this
> area. There are probably some files, that simply need a
> #include "pathnames.h" and some fooDIR -> pathname_foo,
> or the like?
> 
> > Peter
> 
> 
>     Elrond