Give a way to add binaries to the list that shouldn't be messed with by sthread

[simgrid.git] / examples / cpp / actor-exiting / s4u-actor-exiting.tesh

diff --git a/examples/cpp/actor-exiting/s4u-actor-exiting.tesh b/examples/cpp/actor-exiting/s4u-actor-exiting.tesh
index 651cf68914db10775ec3d4b6cc5d14ddd61ce70e..660b0839f59d781e7d987f665cf88f579d07b90f 100644 (file)
--- a/examples/cpp/actor-exiting/s4u-actor-exiting.tesh
+++ b/examples/cpp/actor-exiting/s4u-actor-exiting.tesh
@@ -7,12 +7,12 @@ $ ${bindir:=.}/s4u-actor-exiting ${platfdir}/small_platform.xml "--log=root.fmt:
 > [  2.000000] (maestro@) Actor B terminates now
 > [  3.000000] (maestro@) Actor B gets destroyed now
 > [  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
 > [  3.000000] (maestro@) Actor C terminates now