Change-Id: I266b1cef33e53250da79fac0473c3d45eb740ddb
Reviewed-by: hjk <hjk121@nokiamail.com>

All supported versions have it in that context.

Change-Id: Iafff4760ba521ffc9abc4e05dbbc9263ed6fe21a
Reviewed-by: Orgad Shaneh <orgads@gmail.com>

They are unneeded, some of them are unmaintained

Change-Id: I0ad87e152d8e2328b486b2f904f7cf9613004afe
Reviewed-by: Eike Ziller <eike.ziller@digia.com>

Trying to avoid that round-trip on versions that are known to
not have it puts us on the mercy of detecting the version,
which is unreliable by nature, and bad in practice, as proven
by the recent MinGW builds.

Change-Id: I122eb03fe0ddcb193ed8d45e672564f7113b662f
Reviewed-by: Ray Donnelly <mingw.android@gmail.com>
Reviewed-by: hjk <hjk121@nokiamail.com>

We need to distiguish between start of GDB itself (a.k.a .gdbinit-style
customization) and after the dumper machinery is initialized, which is
nowadays often delayed until the first stop hook.

Change-Id: I40f1e7225c2043b8bcb7d50eef948bb3c9162bb6
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@digia.com>
Reviewed-by: hjk <hjk121@nokiamail.com>

It was in exactly the wrong branch.

Change-Id: I0679c18dc9c049bb89c2cba47cb0762ad81e3024
Reviewed-by: hjk <hjk121@nokiamail.com>

Change-Id: Ic24e7f26228b4f1bc1e7ab3627e86036396584ed
Reviewed-by: hjk <hjk121@nokiamail.com>

Version of gdb < 7.4 means we are on Mac, so we can
disable commands that have known results there.

Change-Id: I8fc97ed61c47af2c3d9e5cc2bf83e97661204d4f
Reviewed-by: hjk <hjk121@nokiamail.com>

We don't support GDB in the range 7.0...7.3 anymore where the
outcome was unsure.

Change-Id: I1ce76f5c4b1febe45c4a3b6404208fed7d9c6868
Reviewed-by: hjk <hjk121@nokiamail.com>

See sourceware.org/bugzilla/show_bug.cgi?id=12023.
The workaround can cause hickups in the output parser
of Mac gdb, as the error message is scattered within
regular output without any markup.

Change-Id: I835133e390403a0f8f6aa573d6f9c63cf0784187
Reviewed-by: hjk <hjk121@nokiamail.com>

Reduce compatibility issues e.g. on Mac. The previous versions
are not working well anyway.

Change-Id: If6cc7c1d4a85300d9bf054966216b52b35c0d1f2
Reviewed-by: hjk <hjk121@nokiamail.com>

This essentially reverts 3aa0e500 , which causes trouble
e.g. for network paths and other corner cases.

Change-Id: I12ceb5fbc68b7a3fc8010165acc910acd2d95e55
Reviewed-by: hjk <hjk121@nokiamail.com>

Mostly internal mimetypes

Change-Id: Ia84206f1334c1f83474cbc307e848719bb98adbc
Reviewed-by: Fawzi Mohamed <fawzi.mohamed@digia.com>
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com>
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>

Was accidentally disabled in 066efcd6.

Change-Id: I64de0609a254aa2914142a4f75105b4140b6ae5b
Reviewed-by: Eike Ziller <eike.ziller@digia.com>

Breakpoints by path are not hit if the path traverses
symbolic links.

Change-Id: I3ab5d1bead8333986444aec709c940840dfddbb4
Reviewed-by: hjk <hjk121@nokiamail.com>

Saves some line noise on the user side.

Change-Id: I9c6d7542195fc7485ac4ee466cd42a28be95b8da
Reviewed-by: David Schulz <david.schulz@digia.com>

Less noise.

Change-Id: I8e533c97207ff5b9c79182c4fb99993f1992154f
Reviewed-by: David Schulz <david.schulz@digia.com>

Fixes a regression introduced by cb857b47

Task-number: QTCREATORBUG-9226
Change-Id: I619df0eb8b5f016aac54a0260eb941fd91a348aa
Reviewed-by: Orgad Shaneh <orgads@gmail.com>
Reviewed-by: hjk <hjk121@nokiamail.com>

Setting breakpoints by file name and line does not work robustly when
using gdb, with neither the full path, nor with just the baseline. Since
typically one of the options work, Creator offers a per-breakpoint choice
of which approach to use. Traditionally, using the full path broke more
often, so the default was "short". Lately (gdb 7.3+) using the full path
seems to be more robust, so the default should be changed. Manual
overriding to "short" is still possible.

Change-Id: I9e857c86a63964bdacf9bebc5444ea752e5974f8
Reviewed-by: hjk <hjk121@nokiamail.com>
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com>

Change-Id: I5a3565179fdd8627387ba01370e6484d668e2160
Reviewed-by: hjk <hjk121@nokiamail.com>

Change-Id: Ie79249039643041fd68da6766b0e6f3ca6080b86
Reviewed-by: hjk <hjk121@nokiamail.com>

The engines know what they want, no need to guess again.

Change-Id: Ie21b0e08eff8b81b217a08d4c47c35c35ae831d7
Reviewed-by: hjk <hjk121@nokiamail.com>

- Split off GDB and LLDB specific parts into separate files,
- Trigger loading of dumpers.py and qttypes.py from bridge.py
- Read start up script at startup, not as part of dumper loading

Change-Id: I7941ee535121fa0f43a466e5bb75a18c9bb19764
Reviewed-by: hjk <hjk121@nokiamail.com>

Change-Id: Ib700afa63739e6d26bdd97225265559d7112eadb
Reviewed-by: hjk <hjk121@nokiamail.com>

This implements the host side of
https://codereview.qt-project.org/#change,50290



Change-Id: I13c7df29534a2a85202c2b295b139896443b0120
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@digia.com>
Reviewed-by: Daniel Teske <daniel.teske@digia.com>
Reviewed-by: BogDan Vatra <bogdan@kde.org>
Reviewed-by: hjk <hjk121@nokiamail.com>

Task-number: QTCREATORBUG-8949
Change-Id: If0cf1c1078a72a3e4a3d371d236bacac858b8046
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>

Change-Id: Ieeffe65be2d7c8f07f41f7211853d616a6aceb85
Reviewed-by: Fawzi Mohamed <fawzi.mohamed@digia.com>

Change-Id: Ia50e61a82101b699390b23b4f1ea9509619314bb
Reviewed-by: hjk <hjk121@nokiamail.com>

This enables the use "official gdb"-styly pretty printers from
within Creator. In case there are both variants, Creator-style
pretty printers are preferred.

Change-Id: Iaa178d922dae4eaa1943e9d5b960a666f80fe4db
Reviewed-by: hjk <hjk121@nokiamail.com>

It's getting crowded...

Change-Id: I24c1a87b013af485743573df7669739ad93f8a89
Reviewed-by: hjk <hjk121@nokiamail.com>

Change-Id: I1c78f5f5a7174002cd25bea109d5fe795530cdb5
Reviewed-by: Daniel Teske <daniel.teske@digia.com>

This is in anticipation of a change of behavior break in the GDB/MI
protocol, see http://permalink.gmane.org/gmane.comp.gdb.patches/83936

.

Change-Id: I135c0a342da1fed13aaedfd9e27499d5ad892c5a
Reviewed-by: David Schulz <david.schulz@digia.com>

Task-number: QTCREATORBUG-8820

Change-Id: If48429fc80d3b928cba4622ff6b168dca8289500
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com>
Reviewed-by: hjk <hjk121@nokiamail.com>

This only worked for distributions with a RedHat/Fedora upstream
so far and requires more dynamicity in the TaskWindow as the
TaskHandler dies with the engine, leading to crashs.

Change-Id: I20d0b3c79e4fd0026cd2a0c9ff5b0a4be22c3121
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>

As we disable of 'by-address' breakpoints by default after each
debugger run as they are unlikely to be correct on the next run,
starting with disabled breakpoints might happen. Disabling it
immediately is faster and less racy than relying on the 'change
needed' mechanism.

Change-Id: Icc5548d322f7ef4f099d218b4f04b4c40e3cb850
Reviewed-by: David Schulz <david.schulz@digia.com>

This avoids a problem when setting the ignore count on a pending
breakpoint.

Task-number: QTCREATORBUG-8809
Change-Id: I8cdeb9c525de33336a21c739c6dc99f824f6fe7a
Reviewed-by: David Schulz <david.schulz@digia.com>

Modern versions of gdb support this and it avoids a nasty
endless loop when setting a condition on a breakpoint in
a non-existing file.

Change-Id: Id3a03a44c016f85617bb1e74a4843b1b398c490f
Reviewed-by: Nikolai Kosjar <nikolai.kosjar@digia.com>

Change-Id: Ie79cdcd5c32a2204ac4b701c253d6d76bd271272
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com>

Change-Id: I241d37793dfde9cfe8e4895039819e91297e6cba
Reviewed-by: hjk <hjk121@nokiamail.com>

This is a recent regression introduced by the delayed python dumper
initialization.

Task-number: QTCREATORBUG-8615
Change-Id: I3b5dbe5b04c68cf873e3a2597edc60fe2888b3c9
Reviewed-by: Orgad Shaneh <orgads@gmail.com>