Steps to reproduce:
1. Follow instructions to compile the blimp engine
2. Run:
   $ ./out-engine/Debug/bin/client_engine_integration run
3. Follow instructions to compile the blimp client
4. Connect the client to the engine.
5. To see client side log, run: 
   $ ./third_party/android_tools/sdk/platform-tools/adb logcat

Expected result:
Logcat works fine.

Actual result:
The blimp connection disconnects, and the follow error message is shown:
$ adb logcat
adb server version (32) doesn't match this client (36); killing...
* daemon started successfully *
--------- beginning of crash

Notes:
There is currently a mismatch between the catapult/devil python library ADB version and the one in the SDK.

This causes issues when running the script for the Blimp engine, since it uses that library:
$ ./out-engine/Debug/bin/client_engine_integration run

If you then later use 'adb logcat' to see the client log, and the path for that points to the checked in version of adb in //third_party/android_tools/sdk/platform-tools, the latter will kill the first, which also includes killing the port forwarding.

These are the version I have after a sync for src@8a274fa60fec11c1c1ddbeb2ee64c3ffb60ca84c :

$ ./third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb version
Android Debug Bridge version 1.0.32
Revision eac51f2bb6a8-android
$ ./third_party/android_tools/sdk/platform-tools/adb version
Android Debug Bridge version 1.0.36
Revision 8f855a3d9b35-android

It would be great if these two binaries could have the same version.