Handle QVariantList within dumpers, as gdb does not resolve
typedefs. Disconnect the gdb process on exit, one more round
of event loop when quitting.

this isn't bullet-proof - integrated error messages are already
translated. but at least we know *where* the message comes from.
also, saves the translators from some pretty useless work.

Reviewed-By: con

Add a corelistener and trigger on shutdown. Notify about critical
states.
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@nokia.com>

Reviewed-by: Roberto Raggi <qtc-committer@nokia.com>

Generalize the concept of the Bluetooth starter, extract base class
BaseCommunicationStarter that can be used to start a serial communication
without further resources (listener) as well. Introduce convenience
functions for both types.

Note: This will only work for COM-ports that are not used otherwise
by the operating system.

Reviewed-By: Oswald Buddenhagen

Should not be necessary when nothing changed in the project info. This
also fixes a problem where include file scanning happened twice after
saving a pro file.

Reviewed-by: Roberto Raggi

- Remove old rfcomm process handler from TrkGdbAdapter, use
  Bluetooth starter instead
- Synchronous connection, remove waitForTrkConnect()
- Move gdb start into Trk version answer, pass on
  settings id hint
- Prevent exit crash triggered by signal gdbProcessFinished()
- Set DebuggerNotReady correctly on AdapterStartFailed when no
  gdb is started yet

Updated the QML front-end to revision 44f3548fde7cf6a87bd3cc8bb1cc0e63cfc5ca4c of qt/kinetic-declarativeui

Fixes a segfault when hovering over QtCleanUpFunction in
qcoreapplication.h.

Reviewed-by: Roberto Raggi <roberto.raggi@nokia.com>

specifically, we need it iff the user gets to see the stopped inferior

seems to have been an artifact from an early version. it was
unreachable (gdb going wild notwithstanding), and would do
Strange Stuff (TM) if it ever were reached.

first, try harder to have an up-to-date sources list.
then, use the mapping whenever applicable and available.

when queuing up commands, don't interrupt if we are already waiting
for interruption. that will be the case when other commands area already
queued.