From bd37b018209faab7713ea9290633ec71bad6c99f Mon Sep 17 00:00:00 2001 From: mquinson Date: Fri, 8 Jun 2007 06:29:13 +0000 Subject: [PATCH] When dealing with an uncatched exception, use CRITICAL after printf. Just in case the error comes from the logging mecanism and to avoiding looping on CRITICALs with no output git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/simgrid/simgrid/trunk@3579 48e7efb5-ca39-0410-a469-dd3cf9ba447f --- src/xbt/ex.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/xbt/ex.c b/src/xbt/ex.c index f758c702c0..075ab2910d 100644 --- a/src/xbt/ex.c +++ b/src/xbt/ex.c @@ -247,7 +247,6 @@ void xbt_ex_display(xbt_ex_t *e) { if (e->remote) bprintf(" on host %s(%ld)",e->host,e->pid); - CRITICAL1("%s",e->msg); fprintf(stderr, "** SimGrid: UNCAUGHT EXCEPTION received on %s(%ld): category: %s; value: %d\n" "** %s\n" @@ -255,6 +254,7 @@ void xbt_ex_display(xbt_ex_t *e) { gras_os_myname(),gras_os_getpid(), xbt_ex_catname(e->category), e->value, e->msg, e->procname,thrower?thrower:" in this process"); + CRITICAL1("%s",e->msg); if (thrower) free(thrower); -- 2.20.1