Skip to content

Debug Log Level

Jump to bottom
foldynl edited this page Nov 24, 2021 · 5 revisions

Under normal circumstances, QLog produces a minimal debug messages. The debug message are printed to standard output (Linux).

QLog implements a debug logging via QLoggingCategory so if an user has a issue and it is requested to be more verbose, the verbosity can be set via OS's environment variable QT_LOGGING_RULES.

An example of usage - very verbose output:

QT_LOGGING_RULES=*.debug=true ./qlog

An example of usage in case when only ADIF formatter is debugged

QT_LOGGING_RULES=qlog.logformat.adiformat.*.debug=true ./qlog

Format of the debug output:

14:35:17.363 [DEBUG ][qlog.logformat.adiformat.function.entered] => OUTPUT [void AdiFormat::writeField(QString, QString, QString):../QLog/logformat/AdiFormat.cpp:201]

where

  • 14:35:17.363 - a timestamp
  • [DEBUG ] - a severity
  • [qlog.logformat.adiformat.function.entered] - logging category
  • OUTPUT - debug message
  • [void AdiFormat::writeField(QString, QString, QString):../QLog/logformat/AdiFormat.cpp:201] - source code entry

Severity levels can be :

  • Critical
  • Debug
  • Info
  • Warning

The Logging Category specifies in which part of the program the debug report was called.

Clone this wiki locally