Skip to content

Debug Log Level

Jump to bottom
Ladislav Foldyna edited this page Jul 1, 2023 · 4 revisions

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

QLog implements debug logging via QLoggingCategory. If a user encounters an issue and requires more verbose output, the verbosity can be set via OS's environment variable QT_LOGGING_RULES.

For example, to enable very verbose output:

QT_LOGGING_RULES=*.debug=true ./qlog

To debug only the ADIF formatter, use:

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

Format of the debug output is:

14:35:17.363 [DEBUG ] [0x7f05083d2440] [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
  • [0x7f05083d2440] - Thread ID
  • [qlog.logformat.adiformat.function.entered] - logging category
  • OUTPUT - debug message
  • [void AdiFormat::writeField(QString, QString, QString):../QLog/logformat/AdiFormat.cpp:201] - source code entry

The Severity levels can be :

  • Critical
  • Debug
  • Info
  • Warning

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

Clone this wiki locally