backtrace in the main editor.

Useful for sending bug reports.

Some categories do not have icons yet, unfortunately.

Task-number: QTCREATORBUG-450

Reviewed-by: Thorbjørn

While before you had to call add, then remove for each context id and
then call update, now you call updateAdditionalContexts with a list of
contexts to remove and add. It has the update step built in.

Reviewed-by: con

* We now consistently avoid punctuation when possible
* Renamed usage of "Inferior" and "Program" to "Application" for
  increased readability
* Fixed inconsistent spacing in front of statusbar label

Reviewed-by:hjk

the previous implementation relied on poking around with setVisible
of the menu actions. Now, command attribute CA_Hide is used instead for
the necessary entries.

Reviewed-by: hjk

Additionally, hiding of debugger menu entries was done as most of
them are irrelevant for QML debugging.

Try to detect engine by looking at toolchain, executable,
attach mode. Find out path to executable in attach to running
dialog.

Reviewed-by: hjk

Needs polishing.

The dependency was there for a while. No need to jump through hoops hoping
to maintain a stand-alone debugger anymore.

editor or re-used an existing one

The new QML Inspector depends on DebuggerPlugin. Also added a dropdown menu into
the debugger toolbar from which the user can select the used debugging
language, e.g. C++ or QML.

Returning a value is not yet supported.

Hidden in the Breakpoints context menu.

thus fixing the exit warning:
"~QX11PixmapData(): QPixmap objects must be destroyed..."

Acked-by: con

doing it in 1.3 as well to avoid possible later conflicts

They were no longer showing e.g. the file name of the diffed file.
Also separate editor id and editor context a bit.

  * Use id() for methods returning a string used to represent
    some type of object.
  * Use displayName() for strings that are meant to be user
    visible.
  * Quieten some warnings while touching the files anyway.
  * Move Factories to their products in the plugins where that
    was not done before.

Reviewed-by: dt

(cherry picked from commit bf077800)

Conflicts:

	src/plugins/debugger/debuggerplugin.cpp
	src/plugins/debugger/gdb/gdboptionspage.ui

(cherry picked from commit 8c52f572)

(cherry picked from commit a5c5cfc4)

Conflicts:

	src/plugins/debugger/debuggerplugin.cpp

Make it possible to trigger a debug-attach in a running instance
of Qt Creator by means of -client, use that in qtcdebugger, thus
enabling it to attaching to crashing executables in run mode
(Windows/CDB).

Modify IPlugin and application so that the complete command line is
serialized and transmitted to a running instance via QtSingleApplication
if -client is specified. Introduce IPlugin::remoteArgument and use that
in core for opening files and in the debugger for attaching.

Use -client in qtcdebugger with some logic to keep it alive as long as
the debuggee, make CDB break in that case as the events are not replayed
correctly in case the debugger is not spawned by the registered handler.
Rubber-stamped-by: con <qtc-committer@nokia.com>

This is part of a bigger change to get rid of the output mode.

Reviewed-by: con

Reviewed-by: hjk

debugging

Long term that would probably better as a run configuration.