Do not call pthread_exit(3) in the desctructor.  This was a phenomenally bad idea since it's highly unlikely that the thread being represented by the object will call its own destructor.  This call has been here for a long, long time (on the order of years), and I'm truly surprised that it never caused problems before now.
Do not call pthread_exit(3) in the desctructor.  This was a phenomenally
bad idea since it's highly unlikely that the thread being represented by
the object will call its own destructor.  This call has been here for a
long, long time (on the order of years), and I'm truly surprised that it
never caused problems before now.

This was causing the test suite to misbehave when stack-allocated thread
objects went out of scope.


git-svn-id: 769d22dfa2d22aad706b9a451492fb87c0735f19@5257 08b38cba-cd3b-11de-854e-f91c5b6e4272

vrjuggler/vrjuggler,LiuKeHua/vrjuggler,godbyk/vrjuggler-upstream-old,MichaelMcDonnell/vrjuggler,MichaelMcDonnell/vrjuggler,MichaelMcDonnell/vrjuggler,LiuKeHua/vrjuggler,vancegroup-mirrors/vrjuggler,godbyk/vrjuggler-upstream-old,vancegroup-mirrors/vrjuggler,MichaelMcDonnell/vrjuggler,LiuKeHua/vrjuggler,vrjuggler/vrjuggler,vrjuggler/vrjuggler,MichaelMcDonnell/vrjuggler,LiuKeHua/vrjuggler,godbyk/vrjuggler-upstream-old,godbyk/vrjuggler-upstream-old,vancegroup-mirrors/vrjuggler,godbyk/vrjuggler-upstream-old,vancegroup-mirrors/vrjuggler,vancegroup-mirrors/vrjuggler,MichaelMcDonnell/vrjuggler,LiuKeHua/vrjuggler,vrjuggler/vrjuggler,vancegroup-mirrors/vrjuggler,godbyk/vrjuggler-upstream-old,vrjuggler/vrjuggler,MichaelMcDonnell/vrjuggler,vrjuggler/vrjuggler,LiuKeHua/vrjuggler,MichaelMcDonnell/vrjuggler,vrjuggler/vrjuggler,LiuKeHua/vrjuggler,vrjuggler/vrjuggler,LiuKeHua/vrjuggler