- 20 Mar, 2019 1 commit
-
-
Script Kiddy authored
In case of conflict in i18n, keep the version of the branch "ours" To resolve a particular conflict, "git checkout --ours path/to/file.desktop"
-
- 07 Mar, 2019 1 commit
-
-
Kevin Funk authored
-
- 25 Feb, 2019 1 commit
-
-
Script Kiddy authored
-
- 24 Feb, 2019 1 commit
-
-
Script Kiddy authored
In case of conflict in i18n, keep the version of the branch "ours" To resolve a particular conflict, "git checkout --ours path/to/file.desktop"
-
- 16 Feb, 2019 1 commit
-
-
Script Kiddy authored
In case of conflict in i18n, keep the version of the branch "ours" To resolve a particular conflict, "git checkout --ours path/to/file.desktop"
-
- 13 Feb, 2019 1 commit
-
-
Script Kiddy authored
-
- 11 Feb, 2019 1 commit
-
-
René J.V. Bertin authored
As per the documentation this will delete the pointer itself when the QSharedPointer refcount drops to 0 That can happen while the target QProcess instance is still running, and will happen occasionally (on Mac), causing a crash. The ChooseCMakeInterfaceJob instance will be deleted soon after a failed connection attempt so there is no need to clear the server pointer here. BUG: 403644
-
- 09 Feb, 2019 1 commit
-
-
Friedrich W. H. Kossebau authored
-
- 08 Feb, 2019 2 commits
-
-
Friedrich W. H. Kossebau authored
GIT_SILENT
-
Gleb Popov authored
Summary: Currently many tests fail (at least on FreeBSD) with ASan turned on. This is what happening: - `test_toolviewtoolbar` creates an action, a `ToolDocument` and a `View` in the `init()` function. - `ToolViewAction` registers itself as event filter for the created `View`. - When `cleanup` is called, the controller gets deleted. This causes removal of its children (`QObject::deleteChildren()`), included the mentioned `View`. - Somewhere later during destruction, some `QEvent` arrives and gets passed to `ToolViewAction::eventFilter()`. This function accesses `->widget()` method of `m_dock->view()`, but that `View` is already deleted, which causes ASan error. Note that adding `removeEventFilter()` to `ToolViewAction::~ToolViewAction()` doesn't solve the problem - the event arrival happens before `ToolViewAction` destruction. Full ASan report: ``` ********* Start testing of TestToolViewToolBar ********* Config: Using QtTest library 5.12.0, Qt 5.12.0 (x86_64-little_endian-lp64 shared (dynamic) release build; by Clang 6.0.1 (tags/RELEASE_601/final 335540)) PASS : TestToolViewToolBar::initTestCase() ================================================================= ==21936==ERROR: AddressSanitizer: heap-use-after-free on address 0x6030000958a0 at pc 0x000800465e5a bp 0x7fffffffd230 sp 0x7fffffffd228 READ of size 8 at 0x6030000958a0 thread T0 #0 0x800465e59 in QScopedPointer<Sublime::ViewPrivate, QScopedPointerDeleter<Sublime::ViewPrivate> >::operator->() const /usr/local/include/qt5/QtCore/qscopedpointer.h:118:16 #1 0x80046352f in Sublime::View::widget(QWidget*) /home/arr/projects/kdevelop/kdevplatform/sublime/view.cpp:76:10 #2 0x800498c53 in ToolViewAction::eventFilter(QObject*, QEvent*) /home/arr/projects/kdevelop/kdevplatform/sublime/idealbuttonbarwidget.cpp:85:40 #3 0x802027193 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) (/usr/local/lib/qt5/libQt5Core.so.5+0x427193) #4 0x80127decb in QApplicationPrivate::notify_helper(QObject*, QEvent*) (/usr/local/lib/qt5/libQt5Widgets.so.5+0x27decb) #5 0x80127f27c in QApplication::notify(QObject*, QEvent*) (/usr/local/lib/qt5/libQt5Widgets.so.5+0x27f27c) #6 0x802026ef0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (/usr/local/lib/qt5/libQt5Core.so.5+0x426ef0) #7 0x802051020 in QObjectPrivate::setParent_helper(QObject*) (/usr/local/lib/qt5/libQt5Core.so.5+0x451020) #8 0x802050c11 in QObject::~QObject() (/usr/local/lib/qt5/libQt5Core.so.5+0x450c11) #9 0x801e4762e in QAbstractAnimation::~QAbstractAnimation() (/usr/local/lib/qt5/libQt5Core.so.5+0x24762e) #10 0x801e4cfa4 in QPropertyAnimation::~QPropertyAnimation() (/usr/local/lib/qt5/libQt5Core.so.5+0x24cfa4) #11 0x802051461 in QObject::event(QEvent*) (/usr/local/lib/qt5/libQt5Core.so.5+0x451461) #12 0x80127dee0 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (/usr/local/lib/qt5/libQt5Widgets.so.5+0x27dee0) #13 0x80127f27c in QApplication::notify(QObject*, QEvent*) (/usr/local/lib/qt5/libQt5Widgets.so.5+0x27f27c) #14 0x802026ef0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (/usr/local/lib/qt5/libQt5Core.so.5+0x426ef0) #15 0x802027db8 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (/usr/local/lib/qt5/libQt5Core.so.5+0x427db8) #16 0x800323331 (/usr/local/lib/qt5/libQt5Test.so.5+0x1e331) #17 0x800323bee (/usr/local/lib/qt5/libQt5Test.so.5+0x1ebee) #18 0x800324988 (/usr/local/lib/qt5/libQt5Test.so.5+0x1f988) #19 0x80032517b in QTest::qRun() (/usr/local/lib/qt5/libQt5Test.so.5+0x2017b) #20 0x800324ef3 in QTest::qExec(QObject*, int, char**) (/usr/local/lib/qt5/libQt5Test.so.5+0x1fef3) #21 0x2b97fb in main /home/arr/projects/kdevelop/kdevplatform/sublime/tests/test_toolviewtoolbar.cpp:144:1 0x6030000958a0 is located 16 bytes inside of 24-byte region [0x603000095890,0x6030000958a8) freed by thread T0 here: #0 0x2b51f2 in operator delete(void*) /usr/src/contrib/compiler-rt/lib/asan/asan_new_delete.cc:149:3 #1 0x800463371 in Sublime::View::~View() /home/arr/projects/kdevelop/kdevplatform/sublime/view.cpp:61:1 #2 0x802050de9 in QObjectPrivate::deleteChildren() (/usr/local/lib/qt5/libQt5Core.so.5+0x450de9) #3 0x802050bf0 in QObject::~QObject() (/usr/local/lib/qt5/libQt5Core.so.5+0x450bf0) #4 0x80041a3be in Sublime::Document::~Document() /home/arr/projects/kdevelop/kdevplatform/sublime/document.cpp:73:21 #5 0x8004626de in Sublime::ToolDocument::~ToolDocument() /home/arr/projects/kdevelop/kdevplatform/sublime/tooldocument.cpp:48:29 #6 0x800462708 in Sublime::ToolDocument::~ToolDocument() /home/arr/projects/kdevelop/kdevplatform/sublime/tooldocument.cpp:48:29 #7 0x802050de9 in QObjectPrivate::deleteChildren() (/usr/local/lib/qt5/libQt5Core.so.5+0x450de9) #8 0x802050bf0 in QObject::~QObject() (/usr/local/lib/qt5/libQt5Core.so.5+0x450bf0) #9 0x800405d9a in Sublime::Controller::~Controller() /home/arr/projects/kdevelop/kdevplatform/sublime/controller.cpp:113:1 #10 0x800405dc8 in Sublime::Controller::~Controller() /home/arr/projects/kdevelop/kdevplatform/sublime/controller.cpp:111:1 #11 0x2b82af in TestToolViewToolBar::cleanup() /home/arr/projects/kdevelop/kdevplatform/sublime/tests/test_toolviewtoolbar.cpp:88:5 #12 0x2bef0c in TestToolViewToolBar::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) /home/arr/projects/kdevelop/build/kdevplatform/sublime/tests/test_toolviewtoolbar_autogen/EWIEGA46WW/moc_test_toolviewtoolbar.cpp:85:21 #13 0x8020320ce in QMetaMethod::invoke(QObject*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) const (/usr/local/lib/qt5/libQt5Core.so.5+0x4320ce) #14 0x800323318 (/usr/local/lib/qt5/libQt5Test.so.5+0x1e318) #15 0x800323bee (/usr/local/lib/qt5/libQt5Test.so.5+0x1ebee) #16 0x800324988 (/usr/local/lib/qt5/libQt5Test.so.5+0x1f988) #17 0x80032517b in QTest::qRun() (/usr/local/lib/qt5/libQt5Test.so.5+0x2017b) #18 0x800324ef3 in QTest::qExec(QObject*, int, char**) (/usr/local/lib/qt5/libQt5Test.so.5+0x1fef3) #19 0x2b97fb in main /home/arr/projects/kdevelop/kdevplatform/sublime/tests/test_toolviewtoolbar.cpp:144:1 previously allocated by thread T0 here: #0 0x2b4612 in operator new(unsigned long) /usr/src/contrib/compiler-rt/lib/asan/asan_new_delete.cc:92:3 #1 0x80041b02e in Sublime::Document::newView(Sublime::Document*) /home/arr/projects/kdevelop/kdevplatform/sublime/document.cpp:117:21 #2 0x80041a604 in Sublime::Document::createView() /home/arr/projects/kdevelop/kdevplatform/sublime/document.cpp:82:18 #3 0x2b6eac in TestToolViewToolBar::init() /home/arr/projects/kdevelop/kdevplatform/sublime/tests/test_toolviewtoolbar.cpp:72:22 #4 0x2beefe in TestToolViewToolBar::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) /home/arr/projects/kdevelop/build/kdevplatform/sublime/tests/test_toolviewtoolbar_autogen/EWIEGA46WW/moc_test_toolviewtoolbar.cpp:84:21 #5 0x8020320ce in QMetaMethod::invoke(QObject*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) const (/usr/local/lib/qt5/libQt5Core.so.5+0x4320ce) #6 0x80032302d (/usr/local/lib/qt5/libQt5Test.so.5+0x1e02d) #7 0x800323bee (/usr/local/lib/qt5/libQt5Test.so.5+0x1ebee) #8 0x800324988 (/usr/local/lib/qt5/libQt5Test.so.5+0x1f988) #9 0x80032517b in QTest::qRun() (/usr/local/lib/qt5/libQt5Test.so.5+0x2017b) #10 0x800324ef3 in QTest::qExec(QObject*, int, char**) (/usr/local/lib/qt5/libQt5Test.so.5+0x1fef3) #11 0x2b97fb in main /home/arr/projects/kdevelop/kdevplatform/sublime/tests/test_toolviewtoolbar.cpp:144:1 SUMMARY: AddressSanitizer: heap-use-after-free /usr/local/include/qt5/QtCore/qscopedpointer.h:118:16 in QScopedPointer<Sublime::ViewPrivate, QScopedPointerDeleter<Sublime::ViewPrivate> >::operator->() const ==21936==ABORTING ``` Subscribers: kdevelop-devel, #kdevelop Tags: #kdevelop Differential Revision: https://phabricator.kde.org/D18463 (cherry picked from commit fbb955c7)
-
- 06 Feb, 2019 1 commit
-
-
Script Kiddy authored
In case of conflict in i18n, keep the version of the branch "ours" To resolve a particular conflict, "git checkout --ours path/to/file.desktop"
-
- 05 Feb, 2019 2 commits
-
-
Aleix Pol Gonzalez authored
-
Aleix Pol Gonzalez authored
Shouldn't be stored as is anywhere, anyway.
-
- 04 Feb, 2019 1 commit
-
-
Friedrich W. H. Kossebau authored
Used by non-Plasma unixoid X-based shells to map windows to desktop files e.g. in launcher UIs, which do not know about _KDE_NET_WM_DESKTOP_FILE and instead expect the WM_CLASS to match the basename of the desktop file by default. StartupWMClass overwrites that default.
-
- 03 Feb, 2019 1 commit
-
-
Friedrich W. H. Kossebau authored
-
- 02 Feb, 2019 1 commit
-
-
Script Kiddy authored
-
- 01 Feb, 2019 1 commit
-
-
Script Kiddy authored
-
- 29 Jan, 2019 1 commit
-
-
Maciej Mrozowski authored
-
- 27 Jan, 2019 1 commit
-
-
René J.V. Bertin authored
Ensure that clazy can always access files list in compile_commands.json regardless of the presence of symlinks in theirs paths and/or in the current process working directory. Differential Revision: https://phabricator.kde.org/D15797
-
- 26 Jan, 2019 2 commits
-
-
David Narváez authored
Summary: This basically ports d56117d6 to the build dir chooser. Test Plan: Create a new project from template (pick any template, any valid name) and add some ridiculously long cmake extra arguments (say, -DTEST=<really long string>), then create a new project again and look at the size of the Extra Arguments combo box. Reviewers: #kdevelop, mwolff Reviewed By: #kdevelop, mwolff Subscribers: mwolff, kdevelop-devel Tags: #kdevelop Differential Revision: https://phabricator.kde.org/D18414
-
Script Kiddy authored
-
- 24 Jan, 2019 1 commit
-
-
Milian Wolff authored
gitlab-ci: add basic CI template for KDE CI See merge request kde/kdevelop!2
-
- 23 Jan, 2019 1 commit
-
-
Bhushan Shah authored
Based on https://invent.kde.org/sysadmin/ci-tooling/wikis/Gitlab-CI
-
- 20 Jan, 2019 3 commits
-
-
Friedrich W. H. Kossebau authored
-
Script Kiddy authored
In case of conflict in i18n, keep the version of the branch "ours" To resolve a particular conflict, "git checkout --ours path/to/file.desktop"
-
Script Kiddy authored
-
- 16 Jan, 2019 1 commit
-
-
Script Kiddy authored
-
- 15 Jan, 2019 3 commits
-
-
René J.V. Bertin authored
CMake already has a default install prefix itself which will be used when KDevelop does not specify one (and which could be non-standard e.g. when CMake is called through a wrapper). Differential Revision: https://phabricator.kde.org/D17255
-
Script Kiddy authored
-
Aleix Pol Gonzalez authored
Don't start using the sharedpointer at some random point in the lifetime of the object. Make sure we don't parent it, as QSharedPointer will try to delete it eventually as well.
-
- 13 Jan, 2019 1 commit
-
-
Script Kiddy authored
-
- 11 Jan, 2019 3 commits
-
-
Friedrich W. H. Kossebau authored
-
Friedrich W. H. Kossebau authored
Test Plan: AppImage still built and starting. Reviewers: #kdevelop, brauch, kfunk Reviewed By: #kdevelop, kfunk Subscribers: kdevelop-devel Tags: #kdevelop Differential Revision: https://phabricator.kde.org/D18175
-
Thomas Schöps authored
Summary: This fixes two issues in how KDevelop's clang plugin handles CUDA files (.cu source files and .cuh headers): 1) Those file types were not treated as source files, therefore if such a file was modified, it was not passed among the list of modified source files to clang for re-parsing. The re-parsing thus incorrectly used the unmodified file on disk instead. This is addressed by the change to documentfinderhelpers.cpp and kdevclang.xml. 2) The patch passes the general code parser settings also to CUDA files (change in parsesession.cpp). This is for example important to get flags such as -std=c++11 that are required for correct parsing. However, it is not correct: the build system may use separate options for CUDA files (e.g., CMake's CUDA_NVCC_FLAGS). But it might still be better than the previous behavior of not passing any options except -xcuda, since it might be somewhat likely that it is a reasonable guess. Additional comments: a) I am not sure whether the change in clanghelpers.cpp is required, but it seems coherent. b) I changed the CUDA mime types in kdevclang.xml to inherit from text/x-c++src/hdr instead of text/x-csrc/hdr since the CUDA files can contain C++ code. c) This patch is not sufficient to enable proper CUDA support. I'll post to the kdevelop-devel mailing list for that. Test Plan: Tested manually. Reviewers: #kdevelop, kfunk Reviewed By: #kdevelop, kfunk Subscribers: kfunk, apol, kdevelop-devel Tags: #kdevelop Differential Revision: https://phabricator.kde.org/D17909
-
- 10 Jan, 2019 2 commits
-
-
René J.V. Bertin authored
ec5477f3 introduced runtime detection of the clang builtin header directory on MS Windows. This commit implements the same behaviour on Unix. Some refactoring and code cleanup too. Differential Revision: https://phabricator.kde.org/D17858
-
Milian Wolff authored
Turns out that my commit bf183ce7 from May 2017 moved the background cleanup task into the foreground thread... Sorry for that! When we connect to the timer event, we must use a context object that lives within the background thread. The thread itself *does not* live in itself! Fix this by passing the timer itself as context and add an assertion to verify we don't ever do this again. BUG: 388743
-
- 09 Jan, 2019 3 commits
-
-
Friedrich W. H. Kossebau authored
Reviewers: #kdevelop, kfunk Reviewed By: #kdevelop, kfunk Subscribers: kfunk, kdevelop-devel Tags: #kdevelop Differential Revision: https://phabricator.kde.org/D17888
-
Kevin Funk authored
BUG: 402617 FIXED-IN: 5.3.2
-
David Narváez authored
Summary: The previous code did not handle folders with multiple actions but no parent. Test Plan: Create a project with two toplevel targets (e.g. a CMakeLists.txt with two add_executable calls), add the project to a KDevelo session, go to Configure Launches and try adding a compiled binary by clicking on the Add button at the top-left corner. Before this patch, only one of the two toplevel targets would show in the menu. Reviewers: #kdevelop, apol Reviewed By: #kdevelop, apol Subscribers: kfunk, apol, arrowd, kdevelop-devel Tags: #kdevelop Differential Revision: https://phabricator.kde.org/D18021
-
- 06 Jan, 2019 1 commit
-
-
Script Kiddy authored
In case of conflict in i18n, keep the version of the branch "ours" To resolve a particular conflict, "git checkout --ours path/to/file.desktop"
-