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>
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>
This helps with MinGW on Linux.
Change-Id: I6495d0606738a8ad540477dcb820c62e0a06f34c
Reviewed-by: Eike Ziller <eike.ziller@nokia.com>
Reviewed-by: hjk <qthjk@ovi.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>
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>
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>
Merges the Project, Qt4 and Tool Chain categories into one Build & Run
category, which makes it finally possible to reduce the minimum height
of the preferences dialog.
Change-Id: I8d94aac9c9531200f5d8ca212a53d3edc5734138
Reviewed-on: http://codereview.qt-project.org/5023
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Daniel Teske <daniel.teske@nokia.com>
If one hits a C++ breakpoint before the QmlEngine is properly set up
the debugging actions are all disabled. Patch 58faedc4e tried to
fix this by automatically executing continue in these cases, but
this let to errors on Mac OS X. Instead just delay the setting of
C++ breakpoints.
Task-number: QTCREATORBUG-5681
Change-Id: I149dea9b453ed7abd33a1a93b5b546d7c6cda8fd
Reviewed-on: http://codereview.qt.nokia.com/2568
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Christiaan Janssen <christiaan.janssen@nokia.com>
The code was changed from #ifdef Q_OS_WIN to
sp.toolChainAbi.osFlavor() == Abi::WindowsMSysFlavor, which means it was
effectively disabled the last 5 months except in very rare cases.
Also Danimo confirms that the code is no longer needed.
Change-Id: Ia99d9d12415757b3d1e329a631cff0d78caf7804
Reviewed-on: http://codereview.qt.nokia.com/2218
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: hjk <qthjk@ovi.com>
Warn if the condition fails, but otherwise don't change the execution
flow.
Change-Id: Id7b14c745109b66960add967b2a4ef8d31e1a546
Reviewed-on: http://codereview.qt.nokia.com/2389
Reviewed-by: Eike Ziller <eike.ziller@nokia.com>
This is mainly a workaround for cases where gdb crashes when setting
this breakpoint. It's unclear so far why this happens, but when it
happens, the debugger is basically useless, so there should be a
way to disable the "bad" feature.
Change-Id: I28ede9b38eb8bf56a8c5998088be487b4ee5896d
Reviewed-by: con
Task-number: QTCREATORBUG-5275
Reviewed-on: http://codereview.qt.nokia.com/1604
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Eike Ziller <eike.ziller@nokia.com>
Use proper QByteArray member in GdbResponse instead. Less magic, and
does not break array-style reponses where all children are assumed to
be of the same "type".
Change-Id: Ief1efdeb0412f59836e1b2d6f4cb751ddef3216e
Reviewed-on: http://codereview.qt.nokia.com/1184
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Eike Ziller <eike.ziller@nokia.com>
