Support remote application debugging

Originally requested for internal developers. Below the original request:

My use-case is usually this:

There is application on device that uses Qt5 libraries.
I log in to device and modify application’s MANIFEST.MF by adding /bin/on --h before entry-point. This is needed only if I want to debug starting the application.
I launch pdebug that works as gdb-server on device
Back to host I start ntoarm-gdb (from devstage), tell it to connect to 169.254.0.1 with given port
Then I say attach to PID
Qt5 sources and symbols I have in local folder that I have pointed to GDB in .gdbinit
Dlopen and other stuff I may need to break at I point through SVNFS, which is just a file path in .gdbinit again (set-solib-search-path)
After setting appropriate breakpoints I give command continue to start the application, it was held in SIGSTOP before because I gave /bin/on --h
Usually I’m not interested in application source or how to build it, more just see what Qt libraries are doing, but if I want, I can also add symbols of application itself.
Regarding QtCreator, I want to use it just as GDB front-end. It’s not the typical use-case for end users, but very useful for us who need to diagnose the system. QtCreator used to be more system agnostic before all the wizards (although setting some things properly were in cryptic places), I think my best shot would be to try to configure 2.5.0 as it doesn’t make conclusions that “ah, you want to debug BlackBerry device, you need to set up this this and this, and if you don’t do this I will not let you click continue here” and “oh, this qmake version is not supported with this device” and “hey, even if you click debug now, the debug doesn’t really try to start as you haven’t set up a project and gone to debug mode, but just for your confusion I did let you choose choose debug from up-menu”.