Use the same setting in CDB, move it to common settings page
in a follow-up commit.
Change-Id: I67d6cd706f658c616a431e9d518d52e020afa54c
Reviewed-by: hjk <qthjk@ovi.com>
Avoid clashes with breakpoints resulting from options
(break at functions from options, potentially using bm).
Change-Id: I3746f5a246d7bbeea36df412460edf3f2a90e2c0
Reviewed-by: hjk <qthjk@ovi.com>
Make the warning label italic, so it still stands out a bit.
Task-number: QTCREATORBUG-8345
Change-Id: Ia8cb4a45817e314411b326ca9e1929e5dbe85f76
Reviewed-by: hjk <qthjk@ovi.com>
Debugger display in separate windows currently opens several
widgets without title at the same location that disappear
below the main window when stepping.
Put them in a tabwidget and raise it when setting new values.
Task-number: QTCREATORBUG-8344
Change-Id: Icb6dd8942ab851aeeb6a9248c4a1360e8841cf61
Reviewed-by: hjk <qthjk@ovi.com>
On a debug break, inspector tools cannot be used as the
gui thread is blocked.
Task-number: QTCREATORBUG-5466
Change-Id: I808d751b1ade7e4a5c98e87fec7bb4cb02715ad8
Reviewed-by: Christiaan Janssen <christiaan.janssen@digia.com>
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
Update context from QML object tree or the stack frame
depending upon debugger engine state.
Change-Id: I4e6affba37acc016513ad95cd278a400aaa18c49
Reviewed-by: Christiaan Janssen <christiaan.janssen@digia.com>
Clicking around QML code in the editor would update
the Inspector. This is now disabled.
The problem with the behaviour is that the object tree
would be expanded and that may be unwelcome for some users.
Also some code snippets may be shared by multiple
objects, for eg. a custom QML component. In this case, the
behaviour was undefined as to which object in the tree would
be selected. This case of 'one-to-many' was not handled. Finally,
the inspector queries for object ids lazily. Hence, sections of
code may not be associated with an id resulting in unknown
behaviour.
Task-number: QTCREATORBUG-8246
Change-Id: I6266fd0767d0619af70387e2e867a756548120ca
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
Without this fix, GDB tries to connect to the gdbserver on the SSH port
when using the "Attach to Running Application" action. This fixes that
to use the proper gdbserver port.
Change-Id: I4ada31693879f28acf8046885d1dd15aff5d748c
Reviewed-by: Fawzi Mohamed <fawzi.mohamed@digia.com>
When an object is selected in the Inspector, the
Editor is updated to show the relevant code.
Task-number: QTCREATORBUG-8246
Change-Id: I4f7fbcccdeb22849682fa72c63e87a78f48d185b
Reviewed-by: hjk <qthjk@ovi.com>
Reviewed-by: Christiaan Janssen <christiaan.janssen@digia.com>
QML objects are fetched lazily when constructing the object tree.
Incase parents have not been previously fetched, we fetch the
required data to construct only the relevant branch of the tree.
Task-number: QTCREATORBUG-8246
Change-Id: Id529c3b2334d33ff4eb46b14f50cf042ad2960e2
Reviewed-by: hjk <qthjk@ovi.com>
Pass both arguments to qmake. The assumption being that most
projects will not mix both Qt Quick 1 and Qt Quick 2. In the
case of others, debugging will be enabled only for the first
debugging client that is enabled. This is inline with the
current behaviour where debugging multiple engines is not
supported.
Change-Id: I90cd6c6ff559a3a7519ee3ee10690c0e8135c97b
Reviewed-by: hjk <qthjk@ovi.com>
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
Distinguish from const char * one.
QString ctor is yet to be removed
Change-Id: I2da231036c6417353b0566d39666d918ad141c6d
Reviewed-by: hjk <qthjk@ovi.com>
If everything is built with 32 bitness there is no need
to call win64interrupt.exe
Task-number: QTCREATORBUG-7891
Change-Id: I1981b0dfd0ff08ff8acce0e5b81858b00f536ded
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com>
Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
Reviewed-by: hjk <qthjk@ovi.com>
The RemoteGdbServerAdapter should be invoked (instead of
LocalPlainGdbAdapter) when using startmode StartRemoteProcess.
Change-Id: I0f4c9dc2a275ef4b42ddf5b425b8dee839c83458
Signed-off-by: Marcus Folkesson <marcus.folkesson@gmail.com>
Reviewed-by: Orgad Shaneh <orgads@gmail.com>
Reviewed-by: hjk <qthjk@ovi.com>
(cherry picked from commit 0b121abb5e)
Give it a color number != 0 and replace the first generated color
(usually very bright) by base color.
Change-Id: I736fa24215974b810f050d8a407ddf4a2432d711
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com>
Factor out and streamline code from the annotation highlighter
to create a list of colors suitable for highlighting and use that
in memory view.
Task-number: QTCREATORBUG-8250
Change-Id: Iefd408847897ddc98e3aecd6e4f084d1415b80c0
Reviewed-by: hjk <qthjk@ovi.com>
Inspector follows a different cycle and its contents are
always valid during a debug session. Show the values in
Locals and Expressions as valid for user to interact
with them.
Task-number: QTCREATORBUG-8167
Change-Id: If2f622de5b8bf6da78571bc007efd19602a5f389
Reviewed-by: hjk <qthjk@ovi.com>
Reviewed-by: Robert Loehning <robert.loehning@digia.com>
Reviewed-by: Eike Ziller <eike.ziller@digia.com>
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
The host address is now retreived from the kit info.
Incase, a device is not associated with the given kit,
the host is assumed to be localhost.
Change-Id: I659d2d64ec78dc1b10c80c97390994a56ff26344
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
Reviewed-by: hjk <qthjk@ovi.com>
Reviewed-by: Eike Ziller <eike.ziller@digia.com>
The start script needs information about the environment to be
really useful.
Provide this information by arguments.
Change-Id: I9e08c2a8785758caecbbcbc3ea4f97014ff1e281
Signed-off-by: Marcus Folkesson <marcus.folkesson@gmail.com>
Reviewed-by: hjk <qthjk@ovi.com>
The RemoteGdbServerAdapter should be invoked (instead of
LocalPlainGdbAdapter) when using startmode StartRemoteProcess.
Change-Id: I0f4c9dc2a275ef4b42ddf5b425b8dee839c83458
Signed-off-by: Marcus Folkesson <marcus.folkesson@gmail.com>
Reviewed-by: Orgad Shaneh <orgads@gmail.com>
Reviewed-by: hjk <qthjk@ovi.com>
