use a user level mallocator on the task content

[simgrid.git] / examples / gras / console / ping_client.c

diff --git a/examples/gras/console/ping_client.c b/examples/gras/console/ping_client.c
index da1abfd..043fc26 100644 (file)
--- a/examples/gras/console/ping_client.c
+++ b/examples/gras/console/ping_client.c
@@ -41,7 +41,7 @@ int client(int argc, char *argv[])
     CATCH(e) {
       if (e.category != system_error)
         /* dunno what happened, let the exception go through */
-        RETHROW0("Unable to connect to the server: %s");
+        RETHROWF("Unable to connect to the server: %s");
       xbt_ex_free(e);
       gras_os_sleep(0.05);
     }
@@ -62,9 +62,9 @@ int client(int argc, char *argv[])
   TRY {
     gras_msg_send(toserver, "ping", &ping);
   }
-  CATCH(e) {
+  CATCH_ANONYMOUS {
     gras_socket_close(toserver);
-    RETHROW0("Failed to send PING to server: %s");
+    RETHROWF("Failed to send PING to server: %s");
   }
   XBT_INFO(">>>>>>>> Message PING(%d) sent to %s:%d <<<<<<<<",
         ping,
@@ -74,9 +74,9 @@ int client(int argc, char *argv[])
   TRY {
     gras_msg_wait(6000, "pong", &from, &pong);
   }
-  CATCH(e) {
+  CATCH_ANONYMOUS {
     gras_socket_close(toserver);
-    RETHROW0("Why can't I get my PONG message like everyone else: %s");
+    RETHROWF("Why can't I get my PONG message like everyone else: %s");
   }
 
   /* 8. Keep the user informed of what's going on, again */