anchor.diff:  
   NOTE: Here is what happens behind the hoods when you press "OK" : +
    1. QtCreator launches gdb... +
  - 2. which will execute the script "start_gdbserver.py" (as required by commands we added in "Additional Startup  Commands")... +
  + 2. which will execute the script "start_gdbserver.py" _(as required by commands we added in "Additional Startup  Commands")_... +
    3. then connect to gdbserver (using the command *"target remote :5039"*) ... +
    4. load the libraries... +
  - 5. and continue the execution of the app !
  + 5. and continue running the app !
   
   
   === 4. Known limitations
  
positive.code: 
  ===== 2.2. gdbserver
  
  First, make sure you have *packaged a copy of "gdbserver"* with the app you want to debug +
  => and call this copy *"libgdbserver.so"*
  
  TIP: And I strongly advise you to set this up in your build pipeline once for all, for every Android debug build. That's what we have done, and that's pretty neat.
  
  NOTE:  The right copy of *"gdbserver"* to use can be found in your *"android-ndk\prebuilt\android-arm\gdbserver\"* directory.
  
  
  Then get a copy of the script https://raw.githubusercontent.com/fw4spl-org/android-cmake/master/start_gdbserver.py, and modify its vars *ANDROID_APK_PACKAGE* and *ACTIVITY_NAME* to match your app. 
  
negative.code: 
  That's it !
  
  Not only will it *"adb pull"* the most important files /system/bin/*app_process* and /system/bin/*linker*, but also the libraries in */system/lib/* and */vendor/lib/*.
  
  For your information  :
  
  