aboutsummaryrefslogtreecommitdiffstats
path: root/src/plugins/valgrind/valgrindengine.cpp
Commit message (Collapse)AuthorAgeFilesLines
* Valgrind: Restructure plugin setuphjk2019-03-251-1/+1
| | | | | | | | | Bring it more in line with the standard pattern. Plus some cosmetics. Change-Id: I2297c4e72892db386c50ece7dc64bdc89f0d9010 Reviewed-by: Christian Stenger <christian.stenger@qt.io>
* ProjectExplorer: Add RunControl accessor to configuration settingshjk2019-03-131-2/+2
| | | | | Change-Id: I30e8f27d4090576d38fe8a778d7fa508ac26cbfa Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
* Avoid some visible uses of RunControl::runConfiguration()hjk2019-03-121-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For a long time, probably from the very beginning, a RunControl was meant to hold (a copy of) data needed for its operation, that was valid at the time of its construction, to be resilient in cases where RunConfiguration setting were changed while the RunControl was running, or to properly re-run with the original settings. Unfortunately, the task was repetitive, as RunConfiguration classes had no generic access to properties / "aspects" and there was was the runConfiguration() accessor (probably for mostly unrelated reasons in the output pane handling) which made the idea of just casting that to the original runConfiguration and access the data directly there appealing, with all the expected consequences. This patch here partially addresses the issue by copying some more of the related data at RunControl construction time and adjust the using code, avoiding most uses of the runConfiguration() accessor in a mostly mechanical matter. Complete removal appears possible, but will be less mechanical in "difficult" plugins like ios, so this is left for later. The new accessors in RunControl are very much ad-hoc, leaving room for improvement, e.g. by consolidating the access to the run config settings aspects with the other runconfig aspects or similar. For now the goal is to remove the runConfiguration() accessor, and to as much as possible fixed data after RunControl setup is finished. Next step would be to officially allow construction of RunControls without a specific RunConfiguration by setting the necessary data independently, removing the need for the various workarounds that are currently used for the purpose of faking (parts of) the effect of the non-existing RunConfiguration or refusing to operate at all, even if it would be possible. Change-Id: If8e5596da8422c70e90f97270389adbe6d0b46f2 Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
* Valgrind: ModernizeAlessandro Portale2018-12-101-1/+1
| | | | | | | modernize-* Change-Id: I6db60dce78cf2575e36caa597b1f095adba34fd9 Reviewed-by: Orgad Shaneh <orgads@gmail.com>
* Valgrind: Strip QLatin1*Orgad Shaneh2018-12-031-6/+6
| | | | | Change-Id: If93ca890ab6d023ab786a5153f50a1dfa03764de Reviewed-by: hjk <hjk@qt.io>
* ProjectExplorer: Rename 'extraAspect' to 'aspect'hjk2018-10-021-1/+1
| | | | | | | | | Using aspects is the standard pattern nowadays, there's nothing 'extra' to them anymore. Change-Id: I446f9d7b1db58a4899e5e44df33ce51f655e7be4 Reviewed-by: hjk <hjk@qt.io> Reviewed-by: Orgad Shaneh <orgads@gmail.com>
* ProjectExplorer: Split IRunConfigurationAspecthjk2018-09-181-2/+2
| | | | | | | | | ... into items that can be used generically in project configurations (ProjectConfigurationAspect) and items that have a choice between global and project settings (GlobalOrProjectAspect) Change-Id: I94831237bdbb18c339eb76eba131bf7f928933d6 Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
* Remove ApplicationLauncher::Modehjk2018-06-051-0/+4
| | | | | | | | | | | | | | | | | | The actual remaining use was to pop up a terminal in some setups where Mode == Console, with a default of Gui meaning "no console". In some downstream uses it was used set to Console (probably to mean "this helper process does not need a gui") but then luckily ignored when actually starting the helper processes. All cases where the console is useful and requested are nowadays RunWorkers belonging to RunConfigurations with a TerminalAspect, so they can directly get the relevant bit from their RunConfiguration without having it part of all StandardRunnables. Change-Id: I1368d5968da5cf672656aebf200ccac8d45335d0 Reviewed-by: Christian Stenger <christian.stenger@qt.io>
* Finish merging Runnable and StandardRunnablehjk2018-05-231-4/+2
| | | | | | | | | | As all Runnables are known to be StandardRunnables, this here essentially replaces all .is<StandardRunnable> by 'true'. .as<StandardRunnable> by no-op, and fixes the fallout. Change-Id: I1632f8e164fa0a9dff063df47a9e191fdf7bbb2e Reviewed-by: Tobias Hunger <tobias.hunger@qt.io> Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
* Valgrind: Show full command-line on valgrind executionOrgad Shaneh2018-01-241-0/+4
| | | | | | Change-Id: I2cc5e966be44cb65f9dda5e55c38538badd78130 Reviewed-by: Tobias Hunger <tobias.hunger@qt.io> Reviewed-by: hjk <hjk@qt.io>
* Valgrind: Better output message for debuggee exit codeshjk2017-08-241-1/+1
| | | | | | | | The values are not "unknown errors", but known to be exit codes of the debuggee. Change-Id: Icc5e99d463269f1f167ab7b49b78b92c2e4c6b65 Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
* ProjectExplorer: Use a real 'finishing' phase for RunControlshjk2017-07-171-1/+0
| | | | | | | | | | | | | | | | | | Instead of a blunt delete() RunControl::initiateFinish() is triggered by the closing of the application output instead. The rampdown process is basically the same as stop() now, except for the other success signal (new finished()) and the final self-destruction of the runcontrol. stop() itself triggers initiateStop() on all running workers in parallel (before it was in the order of start). This gives downstream complex worker combinations the flexibility to use any order it wants by ignoring stop() on 'uninteresting' workers, and centralizing rampdown e.g. in the main worker. That setup should be rare in practice, but seems needed in some profiler cases. Change-Id: I986a152a663754206709ed4df0d4568847afad17 Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
* ProjectExplorer: Move re-runnable decision to RunWorkershjk2017-07-101-1/+1
| | | | | | | | | | | | A RunControl is re-runnable if all its workers are, a RunWorker is re-runnable if it's Stopped and unless it says otherwise. Also ensure SimpleTargetRunner only reportStop() once per run and make process error message re-usable. Change-Id: I73f5fb724d3026ceb81d5e32a3a71b4814b2bca9 Reviewed-by: Christian Stenger <christian.stenger@qt.io>
* Valgrind: Fix Memcheck startup on remote linuxhjk2017-06-281-0/+1
| | | | | | | Remote CallGrind is still dysfunctional. Change-Id: Ib9ab537dc068c94c7e61ac48b1a4b9d655ccb60f Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
* Valgrind: Remove starting() signalhjk2017-06-281-1/+0
| | | | | | | | | | | | | | | | It's only used internally as one-time communication between worker and the *Tool singleton that handles toolbar button states. We basically start immediately after creation of the worker, so any pre-start tool bar specific operations can be done at RunWorker creation time. Medium term, the runworker should proably steer "their" buttons more directly. Change-Id: Id6df703746ece5eebc23507739cd2a92ec55d11d Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
* Valgrind: Add a ValgrindRunner member to the ValgrindToolRunner basehjk2017-06-261-23/+20
| | | | | | | ... instead of having one in each derived class. Change-Id: Icd121ce46b1d161bd2d59eaeaad8363528dc3c23 Reviewed-by: Christian Stenger <christian.stenger@qt.io>
* Debugger, QmlProfiler et al: Replace AnalyzerStartParameterhjk2017-06-161-1/+0
| | | | | | | | | | | ... and QmlProfilerRunner::Configuaration by PE::UrlConnection, and call it 'serverUrl' on the user side. That's the only variant we ever had and avoids "translations" between three structures that are essential the same. Change-Id: I33386b2b8d2a7985ff934f6f8f840de0831bf9c1 Reviewed-by: Christian Stenger <christian.stenger@qt.io>
* Merge remote-tracking branch 'origin/4.3'Orgad Shaneh2017-06-021-2/+5
|\ | | | | | | Change-Id: I56004e3ec9dc9d92d33bdae438c4f7e069eccc45
| * Fix crash when using Valgrind for iOS & AndroidVikas Pachdha2017-05-291-4/+9
| | | | | | | | | | | | | | Task-number: QTCREATORBUG-18254 Change-Id: I49a20edafa1d241c83a301ce9652a6fb839bed93 Reviewed-by: Eike Ziller <eike.ziller@qt.io> Reviewed-by: hjk <hjk@qt.io>
* | Valgrind: Announce 'started', not 'stopped' on startuphjk2017-05-161-1/+1
| | | | | | | | | | | | | | Also provide a name for the workers. Change-Id: I323c498db1eeb8225170aae080fdf084aa53e14a Reviewed-by: Christian Stenger <christian.stenger@qt.io>
* | ProjectExplorer: Split Target and ToolRunners into smaller taskshjk2017-05-151-3/+3
| | | | | | | | | | | | | | | | This increases re-usability of activities like 'port gathering', and makes their use less dependent on actual device implementations. Change-Id: I017cb74874f2b38c487ba2d03906a675d5618647 Reviewed-by: Christian Stenger <christian.stenger@qt.io>
* | ProjectExplorer/Debugger/RL: Make run control state transitions more uniformhjk2017-05-051-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | Forward all tool and target activities to run control, and initiate further state transitions (only) from there. Also, make sure tool/target's on finished() triggered on all finishing code paths. After that, the base state handling is sufficient to handle remote linux running and debugging. Change-Id: I0150ef249c9ad0b7b8ac7192be6dc860c9ca8fc5 Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
* | Valgrind: Move to new target/tool split for local setupshjk2017-05-021-30/+30
| | | | | | | | | | Change-Id: I1167fdc147600c36149c13731d0680b858acf4fb Reviewed-by: Christian Stenger <christian.stenger@qt.io>
* | ProjectExplorer: Add a RunControl::supportsReRunning setterhjk2017-04-071-0/+1
| | | | | | | | | | | | | | | | Removes one reason to derive from base RunControls (specifically ValgrindRunControl). Change-Id: I81e32a49ef30e79ee7e7b53a54021eaaba43453a Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
* | ProjectExplorer: Always initialize RunControl's runnable from RunConfighjk2017-04-061-2/+0
| | | | | | | | | | | | | | That's a good first approximation and often enough all that is needed. Change-Id: If54cdb0e98cda94bc4a4ef24fcc12c78018c4dbe Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
* | ProjectExplorer: Merge AnalyzerRunControl into RunControlhjk2017-04-051-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The change is "conceptually wrong", the AnalyzerRunControl derived classes' functionality should be provided by ToolRunners based classes encapsulating/"being" the current Analyzer*Runner classes. However, the AnalyzerRunControl is only three (empty even) virtual functions, but a big obstacle in merging attempt due to a lot of mechanical followup changes in downstream users. The current construction mechanism of analyzer run controls is actually two different mechanisms (locally direct RunControlFactories, and a "generic" createAnalyzerRunControl wrapper for remote cases). The generic createAnalyzerRunControl makes it difficult to migrated them one-by-one, due to the various downstream users. So instead of merging the per-analyzer two uses directly reduce the "indirection" distance by removing the AnalyzerRunControl intermediate layer. After that the createAnalyzerRunControl mechanism can be dissolved by using normal RunControlFactories also for the remote cases. After that, porting to ToolRunner, and combining with ther local equivalent can be done one by one. Change-Id: I0ddace33fcce210cf3a547ac5bb23b3d85013934 Reviewed-by: Ulf Hermann <ulf.hermann@qt.io> Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
* | ProjectExplorer: Run RunControl::{start,stop} always asynchronouslyhjk2017-03-241-2/+1
|/ | | | | | | | | | | | | | | | This introduces a mini-state-"machine" to handle RunControl states Intialized->[Starting->Running->Stopping->Stopped->]*->Finished. Needing time between trying to start and getting feedback is nowadays the normal setup for all remote targets as well as for most local tools. Making that the default for all runs simplifies the code and provides an opportunity to (a) fix some currently wrong reports of "stopped immediately" and (b) to remove target-specific (WinRT) or tool-specific (Valgrind, GammaRay) state members doing essentially the same. Change-Id: I7f52fee41144188ee8389e922fdc265f8c0a6459 Reviewed-by: David Schulz <david.schulz@qt.io> Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
* ProjectExplorer: Unify RunControl setup/teardownTobias Hunger2017-03-011-12/+3
| | | | | | | | | | | | | | Provide protected methods in RunControl to handle the notification of when the RunControl starts and stops. Use these helpers to move the isRunning() method into the RunConfiguration itself instead of reimplementing it everywhere. Change-Id: Ia8de42f7a6a14a049870d4e7fcb9af6756c2caa4 Reviewed-by: Maurice Kalinowski <maurice.kalinowski@qt.io> Reviewed-by: hjk <hjk@qt.io> Reviewed-by: Ulf Hermann <ulf.hermann@qt.io> Reviewed-by: Christian Kandeler <christian.kandeler@qt.io> Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
* Analyzer: Move toolbar icon specification down to individual RunControlshjk2016-05-311-0/+3
| | | | | | | | Giving individual RunControls the freedom back to decide what they want, even if they currrently decide to use the same one. Change-Id: Ia2acf4b9d32d23c486339b2488611038672aba25 Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
* Make local custom executables run independent of device selectionhjk2016-05-041-2/+3
| | | | | | | Task-number: QTCREATORBUG-16199 Change-Id: I1e9e2103e626c6480fa1c5ac9b2b3f8ac93e3038 Reviewed-by: Christian Kandeler <christian.kandeler@theqtcompany.com> Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
* Valgrind: Clean error view on run control startup againhjk2016-03-101-0/+1
| | | | | | | Fixes a recently introduced regression. Change-Id: Ia36977df87906c320527123f84dd1a347768b06c Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>
* Debugger: Merge debug mode and analyze modehjk2016-03-071-9/+16
| | | | | | | | | | | | | | | | | | | | | | | | On the user-visible side, only the 'Analyze' mode button disappears, and instead a combobox to switch between different tools in appears in the Debug mode toolbar. Internally, that's quite some re-organzition: The centralized 'Analyze mode is busy' flag is gone, allowing us to run e.g. ClangStaticAnalyzer and MemCheck in parallel. Analyzer tools and debugger now share the same mechanism to generate/load/save dock widgets. Analyzer tools now create and handle their own start/stop button when appropriate. In general, Analyzer tools can create/handle more than one run control at a time. Further consolidation is possible, e.g. RunControl state handling could be merged into the base ProjectExplorer::RunControl to avoid the still existing duplication in ~15 instances. Change-Id: I91e5940ebc4211f98056d507cf2f7b5f8efe7f07 Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>
* Move analyzerbase to debuggerhjk2016-02-251-2/+2
| | | | | | | | | | | | This is the first mechanical step to execute on the 'shared pool of debugger/analyzer views' idea. Future steps would be providing infrastructure for the view pool, making all analyzer/debugger views use the pool and then re-extract a sensible base for a 'analyzer-and/or-debugger' tool plugin interface. Change-Id: I1bb392e6dd3084fc56937956bee1d6fd9530335d Reviewed-by: Eike Ziller <eike.ziller@theqtcompany.com>
* Valgrind: Simplify device setup and handlinghjk2016-02-021-6/+5
| | | | | | | | Make isLocal() less intrusively used and correct. Use the stored device more often, also handle errors more quickly. Change-Id: I146d1f5788ea79d0a9d7b058c81908d451cf00d0 Reviewed-by: Christian Kandeler <christian.kandeler@theqtcompany.com>
* Analyzer: Remove AnalyzerRunControl::runnable() and .connection()hjk2016-01-291-4/+6
| | | | | | | | These re-implementations are conceptually "too specific". Rather let the indiviual tools handle there expectations themselves. Change-Id: I0bbea407b2241816a40d19eb1dbb0a7589cbda7b Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>
* Analyzer: Remove explicit environment and runModehjk2016-01-281-17/+1
| | | | | | | Instead, use the one in its (Standard)Runnable. Change-Id: I14dbe91c50d083d11e18d514ec391875c64e3851 Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>
* Analyzer: Remove explicit working directory storage in run controlhjk2016-01-271-1/+0
| | | | | | | | | | | | Instead, use the one in its (Standard)Runnable. The change is mechanical except to the fallback to the project directory which was introduced in 8150209f to keep some compatibility with the previous setup of the Android runner which created and copied the fallback value around and ignored it in the end. Not producing the fallback value is less effort. Change-Id: Ie04da570f0f9fbc1d048f2eacaed522f7253afa3 Reviewed-by: hjk <hjk@theqtcompany.com>
* Analyzer: Use a StandardRunnable instead of an AnalyzerRunnablehjk2016-01-271-4/+3
| | | | | | | ... with a lot potential to code consolidation. Change-Id: I4d3a7fcc1cc6ae8763799f18cf9701695f387791 Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>
* Valgrind: Use StandardRunnable in ValgrindRunner and ValgrindProcesshjk2016-01-261-5/+8
| | | | | Change-Id: I17def50bbf6887b63d676fdb245064f1df2003de Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>
* Valgrind: Random cleanupshjk2016-01-211-5/+1
| | | | | | | Remove unneeded function arguments, Qt 5 connects etc. Change-Id: I95faf80e7b5ccc574e2457b841f7913bc2aa05d3 Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>
* Analyzer: Remove AnalyzerStartParameters from AnalyzerRunControl ctorhjk2016-01-201-3/+2
| | | | | Change-Id: I0f7e982a9144469869e0c42daedfb411789511ca Reviewed-by: Tobias Hunger <tobias.hunger@theqtcompany.com>
* Analyzer: Split AnalyzerStartParametershjk2016-01-201-7/+6
| | | | | | | | | | | ... into AnalyzerRunnable and AnalyzerConnection and use the RunControl's storage instead of an own copy in AnalyzerRunControl. This is an intermediate step on the way to remove AnalyzerStartParameters. Change-Id: Iee7c38781b2fd6ef030dcdada1993684cbb34c74 Reviewed-by: Tobias Hunger <tobias.hunger@theqtcompany.com>
* Update License according to agreement with Free Qt FoundationTobias Hunger2016-01-191-17/+12
| | | | | | | * Update files in src/plugins Change-Id: Ia5d77fad7d19d4bb3498e78661982f68729adb22 Reviewed-by: Tobias Hunger <tobias.hunger@theqtcompany.com>
* Analyzer: Slim down AnalyzerStartParametershjk2016-01-071-5/+16
| | | | | | | | | | | | | | | * SysRoot can always be determined from kit. * Pass around RunMode as extra parameter not as part of AnalyzerStartParameters. That's closer to the pattern used elsewhere. * Environment was always initialized from the runconfig's EnvironmentAspect. The tools can do that directly. * Provide setter for display name for cases where it is not equal to RunConfiguration::displayName Change-Id: I811a0d7cdeb55cc37a16a593b3942abb567a2150 Reviewed-by: BogDan Vatra <bogdan@kdab.com> Reviewed-by: Ulf Hermann <ulf.hermann@theqtcompany.com>
* Valgrind: Start custom actions more directlyhjk2015-06-191-2/+3
| | | | | | | This does not need to go through the PE machinery. Change-Id: If0b2fde5309d7e119e8ac27245a22939b68d847d Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>
* Analyzer: Replace StartMode with a useStartupProject booleanhjk2015-06-171-1/+1
| | | | | | | | | | | | | This is what it is on the top level. The change makes it obvious that in the valgrind(-derived) plugins the value is later wrongly used to make a decision on whether to run the valgrind process locally or remotely. But that's isolated in valgrind now and can be fixed there. Change-Id: I6fa5e669dec1f9e2cdebe42a1591d15144082a21 Reviewed-by: Anton Kreuzkamp <anton.kreuzkamp@kdab.com> Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com> Reviewed-by: Ulf Hermann <ulf.hermann@theqtcompany.com>
* Merge commit '3c85058694ee2e41658d17f524fb48f0b187d2fe'Eike Ziller2015-02-121-6/+6
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: src/libs/utils/tooltip/tipcontents.cpp src/libs/utils/tooltip/tipcontents.h src/plugins/android/androiddeployqtstep.cpp src/plugins/baremetal/baremetalconstants.h src/plugins/baremetal/baremetaldevice.cpp src/plugins/baremetal/baremetaldevice.h src/plugins/baremetal/baremetaldeviceconfigurationwidget.cpp src/plugins/baremetal/baremetaldeviceconfigurationwidget.h src/plugins/baremetal/baremetaldeviceconfigurationwizard.cpp src/plugins/baremetal/baremetaldeviceconfigurationwizardpages.cpp src/plugins/baremetal/baremetaldeviceconfigurationwizardpages.h src/plugins/baremetal/baremetalplugin.cpp src/plugins/baremetal/baremetalplugin.h src/plugins/baremetal/baremetalruncontrolfactory.cpp src/plugins/baremetal/baremetalruncontrolfactory.h src/plugins/cppeditor/cppcodemodelinspectordialog.cpp src/plugins/cppeditor/cppdoxygen_test.cpp src/plugins/cppeditor/cppdoxygen_test.h src/plugins/debugger/breakpointmarker.cpp src/plugins/debugger/debuggeritemmodel.cpp src/plugins/debugger/debuggeritemmodel.h src/plugins/debugger/loadcoredialog.cpp src/plugins/genericprojectmanager/cppmodelmanagerhelper.cpp src/plugins/projectexplorer/addnewmodel.cpp src/plugins/projectexplorer/addnewmodel.h src/plugins/projectexplorer/jsonwizard/jsonfieldpage.cpp src/plugins/qmlprofiler/abstracttimelinemodel.cpp src/plugins/qmlprofiler/abstracttimelinemodel.h src/plugins/qmlprofiler/notesmodel.cpp src/plugins/qmlprofiler/qml/CategoryLabel.qml src/plugins/qmlprofiler/qml/MainView.qml src/plugins/qmlprofiler/qml/Overview.js src/plugins/qmlprofiler/qml/Overview.qml src/plugins/qmlprofiler/qml/TimeDisplay.qml src/plugins/qmlprofiler/qml/TimeMarks.qml src/plugins/qmlprofiler/qmlprofilertimelinemodelproxy.cpp src/plugins/qmlprofiler/sortedtimelinemodel.cpp src/plugins/qmlprofiler/sortedtimelinemodel.h src/plugins/qmlprofiler/timelinemodelaggregator.cpp src/plugins/qmlprofiler/timelinemodelaggregator.h src/plugins/qmlprofiler/timelinerenderer.cpp src/plugins/qmlprofiler/timelinerenderer.h src/plugins/qmlprojectmanager/QmlProjectManager.json.in src/plugins/texteditor/findinfiles.cpp src/plugins/vcsbase/vcsconfigurationpage.cpp src/shared/qbs src/shared/scriptwrapper/interface_wrap_helpers.h src/shared/scriptwrapper/wrap_helpers.h tests/auto/qmlprofiler/abstracttimelinemodel/tst_abstracttimelinemodel.cpp tests/system/suite_debugger/tst_debug_empty_main/test.py tests/system/suite_debugger/tst_qml_js_console/test.py tests/system/suite_debugger/tst_qml_locals/test.py Change-Id: I67540b648f8b162496f4aa606b04d50c7c9125c6
| * Update LicenseEike Ziller2015-01-161-6/+6
| | | | | | | | | | Change-Id: I711d5fb475ef814a1dc9d2822740e827f3f67125 Reviewed-by: Alessandro Portale <alessandro.portale@digia.com>
* | Valgrind: Port to Qt5-style connectOrgad Shaneh2015-02-091-4/+4
| | | | | | | | | | Change-Id: If5f36bb262b932b60133d4301ab614311ce1feee Reviewed-by: hjk <hjk@theqtcompany.com>
* | Misc: Remove unneeded qualificationsOrgad Shaneh2015-02-061-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Mostly done using the following ruby script: Dir.glob('**/*.cpp').each { |file| next if file =~ %r{src/shared/qbs|/qmljs/} s = File.read(file) s.scan(/^using namespace (.*);$/) { ns = $1 t = s.gsub(/^(.*)\b#{ns}::((?!Const)[A-Z])/) { |m| before = $1 char = $2 if before =~ /"|\/\/|\\|using|SIGNAL|SLOT|Q_/ m else before + char end } if t != s puts file File.open(file, 'w').write(t) end } } Change-Id: I919da493d0629b719d328e5e71c96a29d230dfd1 Reviewed-by: Christian Kandeler <christian.kandeler@theqtcompany.com> Reviewed-by: hjk <hjk@theqtcompany.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-08 18:02:11 +0000