A crash can be happen if the back end is slow like a debug build on
windows.
Change-Id: I7352ef2732d29ac60bb0c6d9906c10b7ebefa262
Reviewed-by: Marco Bubke <marco.bubke@qt.io>
Output coming from the debuggee was limited to be printed inside
the DebuggerLog and the Application Output pane, but the output
might be useful to process differently or even additionally to
the default logging.
Provide functionality to be able to add an output processor.
Change-Id: I715b90b28c64d3cf95bcc2a047a5aba1a56d1058
Reviewed-by: hjk <hjk@qt.io>
Make sure that we do not cache incomplete result lists when the search
is canceled (e.g. because the user typed another character).
Task-number: QTCREATORBUG-16753
Change-Id: I5a8f7ab54bed236ccd318841d95a3a4aa4106df0
Reviewed-by: David Schulz <david.schulz@qt.io>
In the general case we don't want the QmlProfilerRunControl to parse
the QML debug port from the application output. As for most platforms
the ports are mapped via some remote connection mechanism the parsed
port is almost certainly wrong.
In the case of local connections, however, the port is actually
correct, so we keep the output parser in the LocalQmlProfilerRunner.
Change-Id: Ifdaae85196d8b034e67bc2ba0b8c05be980b62e5
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
Reviewed-by: hjk <hjk@qt.io>
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
The console output changed even more and now it add one more "OK", in
order to get the right avd name we should stop searching at last "OK".
Task-number: QTCREATORBUG-16783
Change-Id: I2b69763bba740b739e3573fdfae6b6ac9ed16e95
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io>
On shutdown the DebuggerMainWindow might not be alive anymore. By
connecting the signal handler to the window, rather than the plugin we
avoid dereferencing null pointers in that case.
Change-Id: I6421eebc6b1b76f176b31eafeb039d91edd3f0b3
Reviewed-by: hjk <hjk@qt.io>
The already available ClangStaticAnalyzerUnitTests uses the automatically set
up "Desktop" kit to run the analyzer. This is fine for tests that are run in
the build environment of Qt Creator. However, testing different kits on the
same machine means to build Qt Creator itself with those kits, which is not
practical.
The new ClangStaticAnalyzerSessionTests will open the predefined session
"ClangStaticAnalyzerPreconfiguredSession" and for each project and each target
it will run the analyzer. If there is no such session, the test will be
skipped.
To manually preconfigure the desired session:
1. ./qtcreator -settingspath /custom/path
2. Set up the desired kits.
3. Create a session with the name ClangStaticAnalyzerPreconfiguredSession and
load the desired test projects.
To run the test:
./qtcreator -settingspath /custom/path -test ClangStaticAnalyzer,testPreconfiguredSession
Change-Id: I0f027353854088d3acf8acecc16c74e9f0516e7d
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
Already worked with the shortcut defined in the settings, but not with
the standard shortcuts defined by QKeySequence.
Task-number: QTCREATORBUG-16586
Change-Id: I4dc02e29ee5d273c3bfc9de28f52e90cffc2397c
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Height is set to 0 when the pane is hidden, so we have to check the
nonMaximizedSize instead (and only if the pane is not maximized already.
Task-number: QTCREATORBUG-15986
Change-Id: Ic2a08c300a7e311b59c4597d8043041f68a4c1ff
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
Those produce no direct artifacts, so there is no need to check those
Change-Id: Ic10720c1f3c3a7b602c45b870bfd39604754ddee
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
There is UtilityType now, so use that if there is no executable being
generated.
Change-Id: I9e8d512077b8352ec056b49c8db03644482b8fbc
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
The build breaks now with a clear warning if the minimum API level set is less than the minimum required by the kit.
The device dialog also used to show incorrect devices on the first compile cycle in case of the missing manifest file. Now
stock manifest file is used from the kit to analyze the minumun API level for the devices
Task-number: QTCREATORBUG-16740
Change-Id: Icd4d8209dad870cba5f99af1dd700830517f9294
Reviewed-by: BogDan Vatra <bogdan@kdab.com>
The debugger is not executed in the working directory configured for the
run configuration, but in the directory configured in the kit. We have to
cd to the inferior's working directory before execution.
This was broken by 588443b2.
Change-Id: Ib25a82c0cb6e4d1269a2e3fd4bf1f71893005cfa
Reviewed-by: hjk <hjk@qt.io>
For consistency reasons (see "Debugger Console" tool bar), we should use
the *_TOOLBAR icon variants for toolbars. On the other hand, we should
use the icons without *_TOOLBAR for non-toolbar icos (todo list view
items).
Change-Id: I17e7408488112e527c166019341b570ba0f88f10
Reviewed-by: Serhii Moroz <frost.asm@gmail.com>
Reviewed-by: David Schulz <david.schulz@qt.io>
It's only used there. Less code, less disk space.
This code is likely to be copied over and over into future language
plugins.
We cannot afford to spend 1 MB of disk space per build for every 12
lines
of trivial code, so remove this precedent.
Before:
1006824 ./.obj/debug-shared/nimbuildinfo.o
1509784 ./.obj/debug-shared/nimbuildconfigurationfactory.o
After:
1520840 ./.obj/debug-shared/nimbuildconfigurationfactory.o
Change-Id: I8e82b73e50595089d270e52b34cf8bd80ec7e965
Reviewed-by: Filippo Cucchetto <filippocucchetto@gmail.com>
Reviewed-by: hjk <hjk@qt.io>
Setting the mode means resetting all of the UI and repainting the
whole window. This can be painfully slow if the window contains some
large graphical objects, like QML profiler trace.
Change-Id: I64835de49e482826a54e3a844d59bc747ca38370
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
