This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
Re: Debugging Output
- From: Alexander Gottwald <alexander dot gottwald at s1999 dot tu-chemnitz dot de>
- To: "'cygwin-xfree at cygwin dot com'" <cygwin-xfree at cygwin dot com>
- Date: Wed, 5 May 2004 21:17:08 +0200 (MEST)
- Subject: Re: Debugging Output
- References: <BEE0888C52AAFA4A8EE285BFD2FE4C3902AD0BE3@mtvex02.mv.intuit.com>
- Reply-to: cygwin-xfree at cygwin dot com
On Wed, 5 May 2004, Wilks, Dan wrote:
> Alexander Gottwald wrote:
>
> > - debugging output: winDebug(format, args...)
> > - non important configuration messages: winErrorFVerb(2, format, args)
>
> > -logverbose 3...? can give debug messages with differing severity
> > eg -logverbose 3 may print simple traces
> > while -logverbose 10 will also dump all windows messages received
>
> Looking at the #if 0'd logging in windclipboardwndproc would you expect
> that be converted to winDebug (which is logged at level 3) or should it
> be explicitly logged at level 10: winErrorFVerb(10,...) since it's really
> logging window messages?
no. winDebug is sufficient. I was thinking about setting the WM_XXX messages
to a higher loglevel since they may create to many messages.
bye
ago
--
Alexander.Gottwald@s1999.tu-chemnitz.de
http://www.gotti.org ICQ: 126018723