I hit this bug recently using the player/stage robot simulator [1]. Although the main GUI works okay, the amcl driver debug GUI will cause player to crash with the familiar locking assertions. I think that player/stage uses XCD through the C binding.
I know the above description is not totally helpful to someone not familiar with player/stage. I could produce a small testcase configuration after the 15th September if there is interest in reproducing it. For now I just wanted to contribute an actual instance in which this issue has been problematic, and not solvable with the options offered in this thread. In my case, I had to use a Gutsy installation within VirtualBox (which I already had for another regression, this time in kdenlive) to workaround the issue.
I don't really know if the problem is in libxcd or in the use that player makes of it, however.
I hit this bug recently using the player/stage robot simulator [1]. Although the main GUI works okay, the amcl driver debug GUI will cause player to crash with the familiar locking assertions. I think that player/stage uses XCD through the C binding.
I know the above description is not totally helpful to someone not familiar with player/stage. I could produce a small testcase configuration after the 15th September if there is interest in reproducing it. For now I just wanted to contribute an actual instance in which this issue has been problematic, and not solvable with the options offered in this thread. In my case, I had to use a Gutsy installation within VirtualBox (which I already had for another regression, this time in kdenlive) to workaround the issue.
I don't really know if the problem is in libxcd or in the use that player makes of it, however.
[1] http:// playerstage. sf.net