diff options
| author | Christophe Fergeau <cfergeau@redhat.com> | 2015-12-15 18:26:29 +0100 |
|---|---|---|
| committer | Christophe Fergeau <cfergeau@redhat.com> | 2016-01-26 15:58:43 +0100 |
| commit | df56d585cbc928698be6da7476acbc1dffcfcd5b (patch) | |
| tree | 4d9c1f9d061e23bd95ebcbef20bb6135d627478a /python_modules | |
| parent | 417dbedc0b91a7a6aa00c97f7341689cc8de40b2 (diff) | |
| download | spice-common-df56d585cbc928698be6da7476acbc1dffcfcd5b.tar.gz spice-common-df56d585cbc928698be6da7476acbc1dffcfcd5b.tar.xz spice-common-df56d585cbc928698be6da7476acbc1dffcfcd5b.zip | |
log: Add test case for logging code
This gives us a baseline of how the SPICE/glib integration is supposed
to behave.
Everything goes through glib logging facilities, and is impacted by
G_MESSAGES_DEBUG/G_DEBUG=fatal-{warnings,criticals}
Messages in the SPICE_LOG_DOMAIN log domain (output either through
spice_log() or g_log()) will also consider the legacy SPICE_DEBUG_LEVEL
and SPICE_ABORT_LEVEL environment variables. Messages in other domains
will not be impacted by these legacy environment variables.
If spice-common is built without SPICE_DISABLE_ABORT,
spice_return_if_fail()/spice_critical() will abort the program.
g_return_if_fail()/g_critical() will not abort the program.
Diffstat (limited to 'python_modules')
0 files changed, 0 insertions, 0 deletions