From 534d31e4fc62b248c646ad6e19518e8a7b11e048 Mon Sep 17 00:00:00 2001 From: Martin Quinson Date: Tue, 29 May 2012 23:19:02 +0200 Subject: [PATCH] Improve an error message There is good chances that the bug is in the user code (like calling msg_comm_test twice or something similar), and there is nothing we can do reliably from simgrid land if the user land builds such crap. See also https://gforge.inria.fr/tracker/index.php?func=detail&aid=14327&group_id=12&atid=165 --- src/simix/smx_network.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/simix/smx_network.c b/src/simix/smx_network.c index a21f74e4fc..da59e87a51 100644 --- a/src/simix/smx_network.c +++ b/src/simix/smx_network.c @@ -205,9 +205,9 @@ void SIMIX_comm_destroy(smx_action_t action) action, action->comm.refcount, (int)action->state); if (action->comm.refcount <= 0) { - xbt_backtrace_display_current(); - xbt_die("the refcount of comm %p is already 0 before decreasing it. " - "That's a bug!", action); + xbt_backtrace_display_current(); + xbt_die("The refcount of comm %p is already 0 before decreasing it. " + "That's a bug! If you didn't test and/or wait the same communication twice in your code, then the bug is SimGrid's...", action); } action->comm.refcount--; if (action->comm.refcount > 0) -- 2.20.1