I have been facing a problem for quite a while, and I didn't find any
way to solve it.
I am using the player 2.1.1 release which features signals and threads
inherited from the boost library, which is a library that I am used to.
In my application, I connect to a (stage) robot, set the retry limit to
infinity, I set up signals to go to read the different proxies and then
I start the robot thread (PlayerClient::StartThread).
Then I stop the stage simulation and it tries to reconnect. When I
launch stage again, on my client console, a player comment is written
saying that I successfully reconnected to the robot, but then I never
get anything on my signals callbacks.
I first thought that it is a signal program, and that the signals are
not reconnected upon reconnection of the robot, but when I inspect the
backtrace of player, I see that it is blocked into the Read method of
I would like to know how this is supposed to work; if in the
implementation the signals are still connected after a deconnection; if
other people are facing this problem... and hopefully how this can be
Get latest updates about Open Source Projects, Conferences and News.