- Add "Disassemble function..." action with dialog for name
  to stack window.
- Add "Disassemble" with function name from code model to
  the Editor context menu.
- Change the engines to be able to disassemble a function without
  address.

Change-Id: I812f4672d97d9a866ee7f5a38dbd18b2876bccfa
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: I2ff075bcc5607fec9bd9dc8596108ec5f076d48d
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: I62be12e5afe6d2b9a81c03e980e01a49dc4e4632
Reviewed-by: hjk <qthjk@ovi.com>

Just emit the requestRemoteSetup on your own in QmlCppEngine. Also
properly check the related state transitions in DebuggerEngine.

Change-Id: I15dc4236303911126de7eee63ed996bdd8e5c5a8
Reviewed-by: hjk <qthjk@ovi.com>

gdb was not answering to "set breakpoint always-inserted on" at all.

Change-Id: I5fead2e735097236ba094d80bfbd4fa43143e5f7
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: Ifc258886f7d6e7d5b02caae8994210aeef221554
Reviewed-by: Robert Löhning <robert.loehning@nokia.com>

Change-Id: I2b72b34c0cfeafc8bdbaf49b83ff723544f2b6e2
Reviewed-by: Daniel Teske <daniel.teske@nokia.com>

Change-Id: If3c6b5095a10a92683bf2214e45408e8d885085f
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: I13eec92d703e9bb6478f6cc2ba8a125bdd0e3d3e
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: I9b690d9b150c8d162b15370f9f8986267c9128f1
Reviewed-by: Daniel Teske <daniel.teske@nokia.com>

Change-Id: I241401fa010166982e5a95a699c99fbaa87188ef
Reviewed-by: hjk <qthjk@ovi.com>

There is only CODA nowadays.

Change-Id: I8350baed5b66947593c5850491ac9606af3b737c
Reviewed-by: Paweł Polański <pawel.3.polanski@nokia.com>

Change-Id: Iafd07a55e20cd2a65c3bcd23208c24855aeb429f
Reviewed-by: hjk <qthjk@ovi.com>

This does not yet use the potential.

Change-Id: I087311fb7d59b46e49f65a84c4420c72a1227ebb
Reviewed-by: Aurindam Jana <aurindam.jana@nokia.com>

Change-Id: I4eac412f0505efa356bf6e185e8d45d669b9f511
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: I5d45b37e5967804275913c6311741eca83eac539
Reviewed-by: hjk <qthjk@ovi.com>

This was for kernel i386 2.6.24-23-ubuntu and gdb 6.8.
This is pre-python, i.e. not supported anymore.

Change-Id: I1d73dbd6fd7730e15ebab334eb9d043b210eb631
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: I88dc1be2232608bcf158212fcbd6e82db4cad860
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: I730b35f9384d672a613e79842b21709a12b9a95f
Reviewed-by: hjk <qthjk@ovi.com>

Task-number: QTCREATORBUG-6554
Change-Id: I26ea4e5eb5826baaa6fd3bd4b199dd34e88703e0
Reviewed-by: hjk <qthjk@ovi.com>

This is expected to create more console output, which needs to be fixed
on a case-by-case base.

Change-Id: Ic83fb1d4c4392cfb421d9c2eba52b7bae705daae
Reviewed-by: hjk <qthjk@ovi.com>

If the user overrides a dumper function (e.g. threadnames), it is
not overridden when the target is a core dump, because the python
dumpers are re-read after loading the init scripts.

Change-Id: I8740228e754a4ed96352188bdfa4ffec95cdeaa0
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: I29f09f983146fff3301426703db0b93090c6507c
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: I33bd046eca253130049d0a80de7a1a3f3e442307
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: Iac7de58ca8681a60a4b6c9d0e717eb57753898b5
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: Ibe493b4a85d07c4aca64880fd543d14772a3b04b
Reviewed-by: hjk <qthjk@ovi.com>

Task-number: QTCREATORBUG-6178
Change-Id: I3e0a3cae0ee5df02ad8ceee7222bc667e61774c8
Reviewed-by: Robert Löhning <robert.loehning@nokia.com>
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: I409fd58b3e9bb10de50e18e3658790c73e3fd521
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@nokia.com>

Change-Id: Ic84179e34d7ef79016d7646b6502f188c00b0bac
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@nokia.com>

This helps with MinGW on Linux.

Change-Id: I6495d0606738a8ad540477dcb820c62e0a06f34c
Reviewed-by: Eike Ziller <eike.ziller@nokia.com>
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: If18afb5d4665924e7d9250dccbc60a65e6daa75e
Reviewed-by: Eike Ziller <eike.ziller@nokia.com>

Make the second "Abort Debugger" kill the gdb process directly
instead of relying on further communication.

Also fix some "unexpected" (but harmless) state transitions.

Change-Id: I0938ec76420fbd77ec4b7348819dd7f63763547f
Reviewed-by: hjk <qthjk@ovi.com>

External files are still accessible using "source ..."

Change-Id: Icbf27302ef55b9061b69a9274cb7088798adf73d
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: Icec2e3333eb019c51ab32e7bb10887dec1ce9e16
Reviewed-by: hjk <qthjk@ovi.com>

Removal of a breakpoint while the insertion result was pending worked,
but created a lot of noise about unexpected state transitions.

Change-Id: I6c101ee9d184efb1c44f72cbff99b0481f64b0eb
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: Ia4b9c27b8aa405e3e7c6e92639eb105689a0f299
Reviewed-by: hjk <qthjk@ovi.com>

Change-Id: Ia690b5cda84738c303ae7b6bd579e43313728525
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@nokia.com>

Change-Id: I1169f6859810da38d93a8d3e9e9d97e354bedf0b
Reviewed-by: hjk <qthjk@ovi.com>

Previous commit allows to hit cpp breakpoints before the QML engine
is up and running, so there is no need anymore to set breakpoints early
on.

Change-Id: Ia0de490d54057d51c4585c56fa9083de982ba97b
Reviewed-on: http://codereview.qt-project.org/5896


Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Christiaan Janssen <christiaan.janssen@nokia.com>

Change-Id: I49b9375af757117d46ba68301b3f5b241b2f1766
Reviewed-on: http://codereview.qt-project.org/5815


Reviewed-by: hjk <qthjk@ovi.com>