[telepathy-glib/master] Libraries shouldn't set the fatal log level
Sjoerd Simons
sjoerd.simons at collabora.co.uk
Fri Dec 18 09:09:41 PST 2009
A CM should choose by itself it it wants criticals to be fatal, it's not a job
of the library.
Fixes bugs.fd.o#14603
---
telepathy-glib/run.c | 5 -----
1 files changed, 0 insertions(+), 5 deletions(-)
diff --git a/telepathy-glib/run.c b/telepathy-glib/run.c
index f81c558..8db7e39 100644
--- a/telepathy-glib/run.c
+++ b/telepathy-glib/run.c
@@ -210,7 +210,6 @@ tp_run_connection_manager (const char *prog_name,
int argc,
char **argv)
{
- GLogLevelFlags fatal_mask;
DBusConnection *connection = NULL;
TpDBusDaemon *bus_daemon = NULL;
GError *error = NULL;
@@ -222,10 +221,6 @@ tp_run_connection_manager (const char *prog_name,
g_set_prgname (prog_name);
- fatal_mask = g_log_set_always_fatal (G_LOG_FATAL_MASK);
- fatal_mask |= G_LOG_LEVEL_CRITICAL;
- g_log_set_always_fatal (fatal_mask);
-
#ifdef ENABLE_BACKTRACE
g_log_set_handler ("GLib-GObject",
G_LOG_LEVEL_CRITICAL | G_LOG_LEVEL_ERROR |
--
1.5.6.5
More information about the telepathy-commits
mailing list