Fix kill(sigkill/sigterm) signals behaviour on windows

Change-Id: I3b4e2d2e7b32902632522a27e2fc901a7096621a
Reviewed-on: http://gerrit.aldebaran.lan:8080/15005
Reviewed-by: vpaleologue <vpaleologue@aldebaran-robotics.com>
Tested-by: vpaleologue <vpaleologue@aldebaran-robotics.com>
Reviewed-by: proullon <proullon@aldebaran-robotics.com>
Reviewed-by: dmerejkowsky <dmerejkowsky@aldebaran-robotics.com>
Tested-by: gerrit
os: new test for qi::os::kill(pid, SIGKILL)

It does not work, but someone told me orally that it was supposed to work,
even on Windows. In fact it doesn't. Is that a bug then?

Change-Id: I28f454afb1b5c00f5eb5b62304c149a8bcc1f3d1
Reviewed-on: http://gerrit.aldebaran.lan:8080/14988
Reviewed-by: llec <llec@aldebaran-robotics.com>
Tested-by: vpaleologue <vpaleologue@aldebaran-robotics.com>
os: setCurrentThreadName: fix for android

Change-Id: I765e6c8db4955c2721340f4d5595ffc5c389d0c5
Reviewed-on: http://gerrit.aldebaran.lan:8080/14895
Reviewed-by: cgestes <gestes@aldebaran-robotics.com>
Tested-by: cgestes <gestes@aldebaran-robotics.com>
os: doc for getCurrentThreadName

Change-Id: I859fd272bc104f48ba048252eb34f061b39cbefc
Reviewed-on: http://gerrit.aldebaran.lan:8080/14896
Reviewed-by: cgestes <gestes@aldebaran-robotics.com>
Tested-by: cgestes <gestes@aldebaran-robotics.com>
Fix huge WTF, infinite loop at EventLoopThreadPool::destroy.

Wow.

Change-Id: I5cbe87ddc8681a79a2762b7a1e4d67c3fa8b8e64
Reviewed-on: http://gerrit.aldebaran.lan:8080/15033
Reviewed-by: cgestes <gestes@aldebaran-robotics.com>
Reviewed-by: mnottale <mnottale@aldebaran-robotics.com>
Tested-by: mnottale <mnottale@aldebaran-robotics.com>