Refactorize the sthread interception of functions

[simgrid.git] / examples / c / actor-exiting / actor-exiting.tesh

diff --git a/examples/c/actor-exiting/actor-exiting.tesh b/examples/c/actor-exiting/actor-exiting.tesh
index 5833265e7352a1dba31baae95a6c029806ad86ad..4bc56ef830adee1349e1fc6d413dfba4d68d98b6 100644 (file)
--- a/examples/c/actor-exiting/actor-exiting.tesh
+++ b/examples/c/actor-exiting/actor-exiting.tesh
@@ -5,9 +5,9 @@ $ ${bindir:=.}/c-actor-exiting ${platfdir}/small_platform.xml "--log=root.fmt:[%
 > [  3.000000] (C@Ginette) And now, induce a deadlock by waiting for a message that will never come
 >
 >
-> [  3.000000] (maestro@) Oops! Deadlock or code not perfectly clean.
+> [  3.000000] (maestro@) Oops! Deadlock detected, some activities are still around but will never complete. This usually happens when the user code is not perfectly clean.
 > [  3.000000] (maestro@) 1 actors are still running, waiting for something.
 > [  3.000000] (maestro@) Legend of the following listing: "Actor <pid> (<name>@<host>): <status>"
-> [  3.000000] (maestro@) Actor 3 (C@Ginette): waiting for communication activity 0xdeadbeef () in state 0 to finish
+> [  3.000000] (maestro@) Actor 3 (C@Ginette): waiting for communication activity 0xdeadbeef () in state WAITING to finish 
 > [  3.000000] (C@Ginette) I was killed!
 > [  3.000000] (C@Ginette) The backtrace would be displayed here if --log=no_loc would not have been passed