[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Lilypond loglevels & debug output
From: |
Werner LEMBERG |
Subject: |
Re: Lilypond loglevels & debug output |
Date: |
Fri, 05 Aug 2011 19:08:20 +0200 (CEST) |
Very nice, Reinhold!
> The loglevel or debuglevel (whichever we choose) then needs to be
> given as a number, though, like --loglevel=4095
> (i.e. 00011111111111 in binary). Do you have a better idea to
> specify different debug areas?
In FreeType, we have the following (as an environment variable only
since it is a library). From the `DEBUG' documentation file:
FT2_DEBUG
This variable is only used when FreeType is built with
FT_DEBUG_LEVEL_TRACE defined. It contains a list of component
level definitions, following this format:
component1:level1 component2:level2 component3:level3 ...
where `componentX' is the name of a tracing component, as defined
in `fttrace.h', but without the `trace_' prefix. `levelX' is the
corresponding level to use at runtime.
`any' is a special component name that will be interpreted as
`any/all components'. For example, the following definitions
set FT2_DEBUG=any:2 memory:5 io:4 (on Windows)
export FT2_DEBUG="any:2 memory:5 io:4" (on Linux with bash)
both stipulate that all components should have level 2, except for
the memory and io components which will be set to trace levels 5
and 4, respectively.
Werner