| commit | 5fba62adecbb9e7d65966460c16eb6c18d04dbe8 | |
| author | Benjamin Berg <bberg@redhat.com> | |
| Mon, 15 Jan 2018 16:31:21 +0000 (15 17:31 +0100) | ||
| committer | Benjamin Berg <bberg@redhat.com> | |
| Mon, 15 Jan 2018 18:46:22 +0000 (15 19:46 +0100) | ||
| tree | b5c765683c955cb045f32e56c1e9300aad3e3802 | treesnapshot (tar.gz zip) |
| parent | 051d69bbc83cd3aa3d1515a50ba529140352c518 | commitdiff |
gmessages: Flush output stream after logging messages
When debug output is enabled then certain messages will be logged to
stdout. stdout however is block buffered by default when it isn't going
to a TTY meaning that debug logging will not be flushed out properly
when it is being redirected. One example of this happening may be tests
that rely on parsing g_debug messages.
Adding an explicit fflush ensures all log messages will reach the output.
https://bugzilla.gnome.org/show_bug.cgi?id=792432
When debug output is enabled then certain messages will be logged to
stdout. stdout however is block buffered by default when it isn't going
to a TTY meaning that debug logging will not be flushed out properly
when it is being redirected. One example of this happening may be tests
that rely on parsing g_debug messages.
Adding an explicit fflush ensures all log messages will reach the output.
https://bugzilla.gnome.org/show_bug.cgi?id=792432
| glib/gmessages.c | diffblobblamehistory |