From 09af813fef22c2c3cbb34795e290ebab3db65e35 Mon Sep 17 00:00:00 2001
From: Kevin Rocard <kevinx.rocard@intel.com>
Date: Fri, 19 Dec 2014 15:15:50 +0100
Subject: Remove explicit server stop

Stopping the remote-processor in the stop command has two side effect:
 - stopping the remote-processor thread will fail as it is not possible
   to join a thread to itself. This leads to the leak of all the thread
   object (destructor not called).
 - the server will not return the exit command status as it has been
   stopped during it's execution.

Remove the remote-processor stop as it will be called during it's
destruction.

Signed-off-by: Kevin Rocard <kevinx.rocard@intel.com>
---
 test/test-platform/TestPlatform.cpp | 3 ---
 1 file changed, 3 deletions(-)

(limited to 'test/test-platform')

diff --git a/test/test-platform/TestPlatform.cpp b/test/test-platform/TestPlatform.cpp
index a6613e9..9cb45f7 100644
--- a/test/test-platform/TestPlatform.cpp
+++ b/test/test-platform/TestPlatform.cpp
@@ -154,9 +154,6 @@ CTestPlatform::CommandReturn CTestPlatform::exit(
 {
     (void)remoteCommand;
 
-    // Stop local server
-    _pRemoteProcessorServer->stop();
-
     // Release the main blocking semaphore to quit application
     sem_post(&_exitSemaphore);
 
-- 
cgit v1.1