From b5719838ad36fb87c1dcd4469d73e4cb69124e7f Mon Sep 17 00:00:00 2001 From: Dan Breslau Date: Fri, 19 Aug 2016 21:47:33 -0400 Subject: [PATCH] Always print GLib errors to the log as well as stderr --- src/moonshot-logger.vala | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/src/moonshot-logger.vala b/src/moonshot-logger.vala index a559412..b3e05f3 100644 --- a/src/moonshot-logger.vala +++ b/src/moonshot-logger.vala @@ -38,12 +38,10 @@ public MoonshotLogger get_logger(string name) { #if USE_LOG4VALA -// To use this, uncomment the line below that calls Log.set_default_handler. (It's often better -// to let Glib log messages be printed on stderr; but this way, they can be synchronized with -// our log messages in a single stream.) static void glib_default_log_handler(string? log_domain, LogLevelFlags log_level, string message) { Log4Vala.Logger logger = Log4Vala.Logger.get_logger(log_domain ?? "Glib"); + stderr.printf(log_level.to_string() + " : " + message + "\n"); logger.error("Glib error level: " + log_level.to_string() + " : " + message); } @@ -55,7 +53,7 @@ public class MoonshotLogger : Object { public MoonshotLogger(string name) { if (!logger_is_initialized) { - // Log.set_default_handler(glib_default_log_handler); + Log.set_default_handler(glib_default_log_handler); //!! TODO: Don't hard-code the pathname. Log4Vala.init("/home/dbreslau/log4vala.conf"); -- 2.1.4