[kdevelop] [Bug 416007] New: Crash on startup
https://bugs.kde.org/show_bug.cgi?id=416007 Bug ID: 416007 Summary: Crash on startup Product: kdevelop Version: 5.4.6 Platform: Appimage OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com Target Milestone: --- SUMMARY KDevelop crashes every startup on all versions after 5.4.3 STEPS TO REPRODUCE 1. Start KDevelop OBSERVED RESULT Crashes during startup/parsing of project EXPECTED RESULT Should complete parsing properly (like 5.4.3) ADDITIONAL INFORMATION Is there any chance i could get an appImage for kdevelop that has debug symbols so i can get a backtrace? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 406358] New: Kdevelop crashes after closing already closed program
https://bugs.kde.org/show_bug.cgi?id=406358 Bug ID: 406358 Summary: Kdevelop crashes after closing already closed program Product: kdevelop Version: 5.3.2 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com Target Milestone: --- SUMMARY Sometimes after closing a program, kdevelop will still think it is running in the background (it isnt). If you then tell kdevelop to kill the program using the 'stop' functionality, kdevelop will crash. STEPS TO REPRODUCE 1. close and reopen programs using execute until kdevelop thinks there is a program still open when it isnt 2. hit stop and kill the program 3. crash OBSERVED RESULT kdevelop crashes whenever this happens (happened to me twice now) EXPECTED RESULT Kdevelop shouldnt think programs are open when they aren't. It also shouldn't crash even if this scenario does occur (should either just give an error or correct the issue) SOFTWARE/OS VERSIONS Ubuntu 18.04 with 5.3.2 AppImage -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 402309] Code Browser fails to display documentation for Qt functions
https://bugs.kde.org/show_bug.cgi?id=402309 Ian Haber changed: What|Removed |Added CC||master.ha...@gmail.com --- Comment #1 from Ian Haber --- i've seen something similar but different on my version. I get all my qt documentation, but they are shifted by one element (it shows me the documentation for the next item on the list instead) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385298] Deleting external scripts doesn't work
https://bugs.kde.org/show_bug.cgi?id=385298 Ian Haber changed: What|Removed |Added Version|5.1.1 |5.2.4 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385298] Deleting external scripts doesn't work
https://bugs.kde.org/show_bug.cgi?id=385298 --- Comment #1 from Ian Haber --- still not working in 5.2.4 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 397556] kdevelop crashes if you do a project wide search while debugging
https://bugs.kde.org/show_bug.cgi?id=397556 --- Comment #1 from Ian Haber --- Seems like it might be fixed in 5.2.4 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 397556] New: kdevelop crashes if you do a project wide search while debugging
https://bugs.kde.org/show_bug.cgi?id=397556 Bug ID: 397556 Summary: kdevelop crashes if you do a project wide search while debugging Product: kdevelop Version: 5.2.3 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com Target Milestone: --- Kdevelop crashes instantly after you hit the 'search' button while you are debugging (regular execute is fine). Steps to reproduce: 1. debug executable 2. go to project search 3. search for some text 4. crash -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 396710] New: Subclassing interface adds '=0' to header file
https://bugs.kde.org/show_bug.cgi?id=396710 Bug ID: 396710 Summary: Subclassing interface adds '=0' to header file Product: kdevelop Version: 5.2.3 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: file create Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com Target Milestone: --- When creating a file that subclasses an interface, the header file that is generated adds in the =0 on any pure virtual function from the parent class. I dont know if this is intended, but if you are subclassing the interface, chances are you dont want it to still be pure virtual. Also another bug i see with the file creation is on the constructor if you had a parameter that was not required (has a default), such as 'QObject * parent=0', when the file is created, it will not add in the default, so you will end up with just 'QObject * parent'. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 396639] New: variable watch locks up debug if not found
https://bugs.kde.org/show_bug.cgi?id=396639 Bug ID: 396639 Summary: variable watch locks up debug if not found Product: kdevelop Version: 5.2.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: CPP Debugger Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com CC: niko.s...@gmail.com Target Milestone: --- If you watch a variable in gdb so that it will break on change and then close the program, the next time you debug launch, the program will not start. in the kdevelop console, it will just spam: kdevelop.plugins.common: "No symbol \"m_safetyChecksDisabled\" in current context." and not ever start. Another issue along with this is that if this happens and you go to the breakpoints tab in kdevelop, it will lock up the gui after spamming you with popups saying the same thing. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 394612] C++ parsing broken since 5.2.1
https://bugs.kde.org/show_bug.cgi?id=394612 --- Comment #2 from Ian Haber --- Just an update. i updated to ubuntu 18.04 and now everything seems to be working. i dont know what the issue was, but it doesnt seem to affect 18.04 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 394612] C++ parsing broken since 5.2.1
https://bugs.kde.org/show_bug.cgi?id=394612 Ian Haber changed: What|Removed |Added Summary|C++ parsing issue on 5.2.3 |C++ parsing broken since ||5.2.1 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 394612] C++ parsing issue on 5.2.3
https://bugs.kde.org/show_bug.cgi?id=394612 --- Comment #1 from Ian Haber <master.ha...@gmail.com> --- Edit: it looks like it actually broke when going from 5.2.0 to 5.2.1. If you guys have any ideas on what i can try, that would be great. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 394612] New: C++ parsing issue on 5.2.3
https://bugs.kde.org/show_bug.cgi?id=394612 Bug ID: 394612 Summary: C++ parsing issue on 5.2.3 Product: kdevelop Version: 5.2.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com Target Milestone: --- 5.2.3 seems to have an issue parsing all of my header files. getting parse errors for every single line that constructs a value from a member file (especially those that complain that my class isnt a QObject when being passed into the constructor as 'this'). It also seems to have an issue with just random other lines where it just decides not to parse them. i didnt have this issue on 5.2.0, i will go back to 5.2.1 for now because it is completely unusable atm. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 389418] New: Option to not close open program does not work
https://bugs.kde.org/show_bug.cgi?id=389418 Bug ID: 389418 Summary: Option to not close open program does not work Product: kdevelop Version: 5.2.1 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com Target Milestone: --- Whenever you run a program that is already running, it gives you an option to close the current or not close the current running program. Previously when you hit 'dont close', it would run the new program next to the old one. Hitting 'close' would close the old one. The current behavior is broken. When you hit 'dont close', it just keeps asking you if you want to close instead of just running the program. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379750] menu bar sometimes screws up royally, requiring restart to fix
https://bugs.kde.org/show_bug.cgi?id=379750 --- Comment #4 from Ian Haber <master.ha...@gmail.com> --- I attempted to test it by installing the kde desktop environment, but i couldnt even get the menu bars to show up (on any apps). I will have to set up a virtual machine at some point when i get an opportunity. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379750] menu bar sometimes screws up royally, requiring restart to fix
https://bugs.kde.org/show_bug.cgi?id=379750 --- Comment #2 from Ian Haber <master.ha...@gmail.com> --- Has anyone taken a look at this? at least twice a day i have to restart the program because it breaks all the menus. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385298] New: Deleting external scripts doesn't work
https://bugs.kde.org/show_bug.cgi?id=385298 Bug ID: 385298 Summary: Deleting external scripts doesn't work Product: kdevelop Version: 5.1.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com Target Milestone: --- When you delete an external script and reload kdevelop, it comes back. steps to reproduce: 1.Add external script 2.Close/reopen kdevelop 3.Remove the external script 4.Close/reopen kdevelop expected behavior: obviously the script should be gone when you reopen kdevelop actual behavior: script is back in the list. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 383876] Parser stops work when I have opened several files
https://bugs.kde.org/show_bug.cgi?id=383876 Ian Haber <master.ha...@gmail.com> changed: What|Removed |Added CC||master.ha...@gmail.com --- Comment #1 from Ian Haber <master.ha...@gmail.com> --- I have seen this issue. the immediate fix (assuming your parser isnt stuck, which happens sometimes) is to reload the file. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 382960] New: Single quote when completing open quotes
https://bugs.kde.org/show_bug.cgi?id=382960 Bug ID: 382960 Summary: Single quote when completing open quotes Product: kdevelop Version: 5.1.1 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: All editors Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com Target Milestone: --- If i hit the quote key before text, it will do a single quote, but if i hit it after text, i get a double quote. Is there any way it can know that there is an unfinished quote in this scenario and just use a single quote? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379854] kdevelop crashes after closing splitview
https://bugs.kde.org/show_bug.cgi?id=379854 --- Comment #14 from Ian Haber <master.ha...@gmail.com> --- yea, i cant run valgrind on the appimage. luckily this is a crash that is totally avoidable. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379854] kdevelop crashes after closing splitview
https://bugs.kde.org/show_bug.cgi?id=379854
--- Comment #11 from Ian Haber <master.ha...@gmail.com> ---
Yes, thread 1 is the one that crashed.
it doesn't matter which filetype i open. i have tried .c, .cpp, cmakelists.txt,
.gitignore, .csv.
i dont really have any special formatter settings, especially not for txt and
csv files.
Thread 1 "kdevelop" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fb07cb94740 (LWP 29681)]
0x7fb0764a6ff0 in __dynamic_cast ()
from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
bt
#0 0x7fb0764a6ff0 in __dynamic_cast ()
from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#1 0x7fb07c610348 in KDevelop::DocumentController::activeDocument() const
() from /tmp/.mount_kP4amF/usr/lib/libKDevPlatformShell.so.10
#2 0x7fb07c64781e in
KDevelop::SourceFormatterController::updateFormatTextAction() () from
/tmp/.mount_kP4amF/usr/lib/libKDevPlatformShell.so.10
#3 0x7fb07c64e672 in QtPrivate::FunctorCall<QtPrivate::IndexesList<>,
QtPrivate::List<>, void, void
(KDevelop::SourceFormatterController::*)()>::call(void
(KDevelop::SourceFormatterController::*)(),
KDevelop::SourceFormatterController*, void**) () from
/tmp/.mount_kP4amF/usr/lib/libKDevPlatformShell.so.10
#4 0x7fb07c64e2af in void QtPrivate::FunctionPointer::call<QtPrivate::List<>, void>(void
(KDevelop::SourceFormatterController::*)(),
KDevelop::SourceFormatterController*, void**) ()
from /tmp/.mount_kP4amF/usr/lib/libKDevPlatformShell.so.10
#5 0x7fb07c64d7dd in QtPrivate::QSlotObject, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) ()
from /tmp/.mount_kP4amF/usr/lib/libKDevPlatformShell.so.10
#6 0x7fb076a3a5b6 in QMetaObject::activate(QObject*, int, int, void**) ()
from /tmp/.mount_kP4amF/usr/lib/libQt5Core.so.5
#7 0x7fb07af42547 in
KDevelop::IDocumentController::documentClosed(KDevelop::IDocument*) ()
from /tmp/.mount_kP4amF/usr/lib/libKDevPlatformInterfaces.so.10
---Type to continue, or q to quit---
#8 0x7fb07c60ed86 in
KDevelop::DocumentController::notifyDocumentClosed(Sublime::Document*) () from
/tmp/.mount_kP4amF/usr/lib/libKDevPlatformShell.so.10
#9 0x7fb07c61b08e in QtPrivate::FunctorCall<QtPrivate::IndexesList<0>,
QtPrivate::List<Sublime::Document*>, void, void
(KDevelop::DocumentController::*)(Sublime::Document*)>::call(void
(KDevelop::DocumentController::*)(Sublime::Document*),
KDevelop::DocumentController*, void**) ()
from /tmp/.mount_kP4amF/usr/lib/libKDevPlatformShell.so.10
#10 0x7fb07c61ac6d in void QtPrivate::FunctionPointer::call<QtPrivate::List<Sublime::Document*>,
void>(void (KDevelop::DocumentController::*)(Sublime::Document*),
KDevelop::DocumentController*, void**) ()
from /tmp/.mount_kP4amF/usr/lib/libKDevPlatformShell.so.10
#11 0x7fb07c61a117 in QtPrivate::QSlotObject, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) ()
from /tmp/.mount_kP4amF/usr/lib/libKDevPlatformShell.so.10
#12 0x7fb076a3a5b6 in QMetaObject::activate(QObject*, int, int, void**) ()
from /tmp/.mount_kP4amF/usr/lib/libQt5Core.so.5
#13 0x7fb07b88c777 in Sublime::Document::aboutToDelete(Sublime::Document*)
() from /tmp/.mount_kP4amF/usr/lib/libKDevPlatformSublime.so.10
#14 0x7fb07b88cca9 in Sublime::DocumentPrivate::removeView(Sublime::View*)
() from /tmp/.mount_kP4amF/usr/lib/libKDevPlatformSublime.so.10
#15 0x7fb07b88be86 in
Sublime::Document::createView()::{lambda(QObject*)#1}:---Type to
continue, or q to quit---
:operator()(QObject*) const ()
from /tmp/.mount_kP4amF/usr/lib/libKDevPlatformSublime.so.10
#16 0x7fb07b88cbbd in QtPrivate::FunctorCall<QtPrivate::IndexesList<0>,
QtPrivate::List<QObject*>, void,
Sublime::Document::createView()::{lambda(QObject*)#1}>::call({lambda(QObject*)#1}&,
void**) ()
from /tmp/.mount_kP4amF/usr/lib/libKDevPlatformSublime.so.10
#17 0x7fb07b88cb47 in void
QtPrivate::Functor<Sublime::Document::createView()::{lambda(QObject*)#1},
1>::call<QtPrivate::List<QObject*>, void>({lambda(QObject*)#1}&, void*,
{lambda(QObject*)#1}&*) ()
from /tmp/.mount_kP4amF/usr/lib/libKDevPlatformSublime.so.10
#18 0x7fb07b88cae2 in
QtPrivate::QFunctorSlotObject<Sublime::Document::createView()::{lambda(QObject*)#1},
1, QtPrivate::List<QObject*>, void>::impl(int, QtPrivate::QSlotObjectBase*,
QObject*, void**, bool*) ()
from /tmp/.mount_kP4amF/usr/lib/libKDevPlatformSublime.so.10
#19 0x7fb076a3a5b6 in QMetaObject::activate(QObject*, int, int, void**) ()
from /tmp/.mount_kP4amF/usr/lib/libQt5Core.so.5
#20 0x7fb076a3ac8f in QObject::destroyed(QObject*) ()
from /tmp/.mount_kP4amF/usr/lib/libQt5Core.so.5
#21 0x7fb076a417c5 in QObject::~QObject() ()
from /tmp/.mount_kP4amF/usr/lib/libQt5Core.so.5
#22 0x7fb07b89e229 in Sublime::View::~View() ()
from /tmp/.mount_kP4amF/usr/lib
[kdevelop] [Bug 379854] kdevelop crashes after closing splitview
https://bugs.kde.org/show_bug.cgi?id=379854 --- Comment #9 from Ian Haber <master.ha...@gmail.com> --- got the backtrace finally. (gdb) thread apply all bt Thread 17 (Thread 0x7fbef089e700 (LWP 25024)): #0 0x7fbf4c4bcb5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fbf4d2ec1c2 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /tmp/.mount_vF1m0a/usr/lib/libQt5Core.so.5 #2 0x7fbf4d2ed8aa in QEventDispatcherUNIX::processEvents(QFlags) () from /tmp/.mount_vF1m0a/usr/lib/libQt5Core.so.5 #3 0x7fbf4d29e7fa in QEventLoop::exec(QFlags) () from /tmp/.mount_vF1m0a/usr/lib/libQt5Core.so.5 #4 0x7fbf4d0d2d6c in QThread::exec() () from /tmp/.mount_vF1m0a/usr/lib/libQt5Core.so.5 #5 0x7fbf4a4f5e18 in KDevelop::CompletionWorkerThread::run() () from /tmp/.mount_vF1m0a/usr/lib/libKDevPlatformLanguage.so.10 #6 0x7fbf4d0d76a6 in ?? () from /tmp/.mount_vF1m0a/usr/lib/libQt5Core.so.5 #7 0x7fbf453976ba in start_thread (arg=0x7fbef089e700) at pthread_create.c:333 #8 0x7fbf4c4c882d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 16 (Thread 0x7fbef9b92700 (LWP 25023)): #0 0x7fbf4c4bcb5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fbf4d2ec1c2 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /tmp/.mount_vF1m0a/usr/lib/libQt5Core.so.5 ---Type to continue, or q to quit--- #2 0x7fbf4d2ed8aa in QEventDispatcherUNIX::processEvents(QFlags) () from /tmp/.mount_vF1m0a/usr/lib/libQt5Core.so.5 #3 0x7fbf4d29e7fa in QEventLoop::exec(QFlags) () from /tmp/.mount_vF1m0a/usr/lib/libQt5Core.so.5 #4 0x7fbf4d0d2d6c in QThread::exec() () from /tmp/.mount_vF1m0a/usr/lib/libQt5Core.so.5 #5 0x7fbf4a4f5e18 in KDevelop::CompletionWorkerThread::run() () from /tmp/.mount_vF1m0a/usr/lib/libKDevPlatformLanguage.so.10 #6 0x7fbf4d0d76a6 in ?? () from /tmp/.mount_vF1m0a/usr/lib/libQt5Core.so.5 #7 0x7fbf453976ba in start_thread (arg=0x7fbef9b92700) at pthread_create.c:333 #8 0x7fbf4c4c882d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 15 (Thread 0x7fbefb7fe700 (LWP 25014)): #0 0x7fbf4c4bcb5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fbf4d2ec1c2 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /tmp/.mount_vF1m0a/usr/lib/libQt5Core.so.5 #2 0x7fbf4d2ed8aa in QEventDispatcherUNIX::processEvents(QFlags) () from /tmp/.mount_vF1m0a/usr/lib/libQt5Core.so.5 #3 0x7fbf4d29e7fa in QEventLoop::exec(QFlags) () from /tmp/.mount_vF1m0a/usr/lib/libQt5Core.so.5 #4 0x7fbf4d0d2d6c in QThread::exec() () ---Type to continue, or q to quit--- from /tmp/.mount_vF1m0a/usr/lib/libQt5Core.so.5 #5 0x7fbf4a4f5e18 in KDevelop::CompletionWorkerThread::run() () from /tmp/.mount_vF1m0a/usr/lib/libKDevPlatformLanguage.so.10 #6 0x7fbf4d0d76a6 in ?? () from /tmp/.mount_vF1m0a/usr/lib/libQt5Core.so.5 #7 0x7fbf453976ba in start_thread (arg=0x7fbefb7fe700) at pthread_create.c:333 #8 0x7fbf4c4c882d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 13 (Thread 0x7fbf12d60700 (LWP 24987)): #0 0x7fbf4c4bcb5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fbf4d2ec1c2 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /tmp/.mount_vF1m0a/usr/lib/libQt5Core.so.5 #2 0x7fbf4d2ed8aa in QEventDispatcherUNIX::processEvents(QFlags) () from /tmp/.mount_vF1m0a/usr/lib/libQt5Core.so.5 #3 0x7fbf4d29e7fa in QEventLoop::exec(QFlags) () from /tmp/.mount_vF1m0a/usr/lib/libQt5Core.so.5 #4 0x7fbf4d0d2d6c in QThread::exec() () from /tmp/.mount_vF1m0a/usr/lib/libQt5Core.so.5 #5 0x7fbf4d0d76a6 in ?? () from /tmp/.mount_vF1m0a/usr/lib/libQt5Core.so.5 #6 0x7fbf453976ba in start_thread (arg=0x7fbf12d60700) at pthread_create.c:333 #7 0x7fbf4c4c882d in clone () ---Type to continue, or q to quit--- at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 12 (Thread 0x7fbefbfff700 (LWP 24984)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fbf4d0d847b in QWaitCondition::wait(QMutex*, unsigned long) () from /tmp/.mount_vF1m0a/usr/lib/libQt5Core.so.5 #2 0x7fbf49278a47 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /tmp/.mount_vF1m0a/usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fbf4927c6d8 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /tmp/.mount_vF1m0a/usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fbf49277cc9 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /tmp/.mount_vF1m0a/usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fbf4927c722 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /tmp/.mount_vF1m0a/usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fbf49277cc9 in ThreadWeaver::
[kdevelop] [Bug 379854] kdevelop crashes after closing splitview
https://bugs.kde.org/show_bug.cgi?id=379854 --- Comment #8 from Ian Haber <master.ha...@gmail.com> --- Thread 1 "kdevelop" received signal SIGSEGV, Segmentation fault. [Switching to LWP 24069] 0x1fe0af93 in ?? () (gdb) thread apply all bt Thread 16 (LWP 24142): #0 0x1f591b5d in ?? () Backtrace stopped: Cannot access memory at address 0xb7ffec50 Thread 15 (LWP 24133): #0 0x1f591b5d in ?? () Backtrace stopped: Cannot access memory at address 0xd13d5c50 Thread 14 (LWP 24132): #0 0x1f591b5d in ?? () Backtrace stopped: Cannot access memory at address 0xd233dc50 Thread 13 (LWP 24127): #0 0x1f591b5d in ?? () Backtrace stopped: Cannot access memory at address 0xee6c8d10 Thread 12 (LWP 24121): #0 0x18472360 in ?? () Backtrace stopped: Cannot access memory at address 0xd2ffcbf0 Thread 11 (LWP 24120): #0 0x18472360 in ?? () ---Type to continue, or q to quit--- Backtrace stopped: Cannot access memory at address 0xd37fdb30 Thread 10 (LWP 24119): #0 0x18472360 in ?? () Backtrace stopped: Cannot access memory at address 0xd3ffeb90 Thread 9 (LWP 24118): #0 0x18472360 in ?? () Backtrace stopped: Cannot access memory at address 0xed6c6a10 Thread 8 (LWP 24117): #0 0x18472360 in ?? () Backtrace stopped: Cannot access memory at address 0xf4afec50 Thread 7 (LWP 24116): #0 0x18472360 in ?? () Backtrace stopped: Cannot access memory at address 0xedec7d10 Thread 6 (LWP 24115): #0 0x18472360 in ?? () Backtrace stopped: Cannot access memory at address 0xecec5cb0 Thread 5 (LWP 24078): ---Type to continue, or q to quit--- #0 0x1f591b5d in ?? () Backtrace stopped: Cannot access memory at address 0xf73c5c50 Thread 4 (LWP 24077): #0 0x18472709 in ?? () Backtrace stopped: Cannot access memory at address 0x142de0 Thread 3 (LWP 24071): #0 0x1f591b5d in ?? () Backtrace stopped: Cannot access memory at address 0xbb09ce0 Thread 2 (LWP 24070): #0 0x1f591b5d in ?? () Thread 1 (LWP 24069): #0 0x1fe0af93 in ?? () Backtrace stopped: Cannot access memory at address 0xb2641c20 maybe it is stack corruption? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379854] kdevelop crashes after closing splitview
https://bugs.kde.org/show_bug.cgi?id=379854 --- Comment #6 from Ian Haber <master.ha...@gmail.com> --- is there a way for you guys to build a debug version of the appimage? that might help out a lot. I cant build the master atm. my two versions of qt are incompatible. the version of qt that is in the 16.04 repo is too low for QProcess::errorOccurred. the version i develop with is to new and doesnt have QtWebkit. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379854] kdevelop crashes after closing splitview
https://bugs.kde.org/show_bug.cgi?id=379854 --- Comment #5 from Ian Haber <master.ha...@gmail.com> --- nope, just says it cant access the memory for the backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379854] kdevelop crashes after closing splitview
https://bugs.kde.org/show_bug.cgi?id=379854 --- Comment #3 from Ian Haber <master.ha...@gmail.com> --- it still crashes in 5.1.1. I'm currently building from master atm. Is there any way to actually get the backtrace from the appimage? i run it through gdb but whenever it crashes it just says no backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379750] menu bar sometimes screws up royally, requiring restart to fix
https://bugs.kde.org/show_bug.cgi?id=379750 --- Comment #1 from Ian Haber <master.ha...@gmail.com> --- Created attachment 105617 --> https://bugs.kde.org/attachment.cgi?id=105617=edit picture of menu bar incorrect menus this one doesnt have the correct menus. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379854] kdevelop crashes after closing splitview
https://bugs.kde.org/show_bug.cgi?id=379854 --- Comment #1 from Ian Haber <master.ha...@gmail.com> --- only crashes if the splitview is the only thing open when it closes. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379854] New: kdevelop crashes after closing splitview
https://bugs.kde.org/show_bug.cgi?id=379854 Bug ID: 379854 Summary: kdevelop crashes after closing splitview Product: kdevelop Version: 5.1.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: All editors Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com Target Milestone: --- kdevelop crashes if you close splitview in a specific order. steps to recreate: 1. open a file 2. splitview the file 3. close the original (left or top) 4. close the split view. crashes 100% of the time. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379750] New: menu bar sometimes screws up royally, requiring restart to fix
https://bugs.kde.org/show_bug.cgi?id=379750 Bug ID: 379750 Summary: menu bar sometimes screws up royally, requiring restart to fix Product: kdevelop Version: 5.1.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com Target Milestone: --- Created attachment 105478 --> https://bugs.kde.org/attachment.cgi?id=105478=edit picture of menu bar missing items. Occasionally the menu bar on kdevelop messes up and does strange things. I havent found what causes it yet, but it seems to be pretty random. A few of the issues i've found: 1. randomly adding strange menus to the menu bar 3. randomly removing menus from the menu bar. 2. dropdowns for menus being empty when they normally have items in it. i have attached a screenshot that shows one of these issues. As you can see from the screenshot, the run menu is empty. (at this moment, almost all of my menu bars are empty). -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379263] Sometimes digits can't be typed
https://bugs.kde.org/show_bug.cgi?id=379263 Ian Haber <master.ha...@gmail.com> changed: What|Removed |Added CC||master.ha...@gmail.com --- Comment #2 from Ian Haber <master.ha...@gmail.com> --- saving the file fixes this? i've always had to close down kdevelop to fix it here. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 348945] Kdevelop crashed when I removed a breakpoint in the debugger
https://bugs.kde.org/show_bug.cgi?id=348945 Ian Haber <master.ha...@gmail.com> changed: What|Removed |Added CC||master.ha...@gmail.com --- Comment #1 from Ian Haber <master.ha...@gmail.com> --- I'm still seeing this occasionally in 5.1. it is pretty rare, but sometimes after clicking off a breakpoint it doesnt click off the breakpoint but instead moves it a line up. if you click on it at this point, kdevelop will crash. i've been trying to get a backtrace for this for a while but it only happens once in a blue moon. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378223] New: Request: markdown preview
https://bugs.kde.org/show_bug.cgi?id=378223 Bug ID: 378223 Summary: Request: markdown preview Product: kdevelop Version: 5.1.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: all editors Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com Target Milestone: --- How difficult would it be to have a markdown preview in kdevelop? I would also love a hotkey that reformats the markdown tables so they are neat in the source code. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377934] KDevelop's toolviews should be normal windows when undocked.
https://bugs.kde.org/show_bug.cgi?id=377934 Ian Haber <master.ha...@gmail.com> changed: What|Removed |Added CC||master.ha...@gmail.com --- Comment #1 from Ian Haber <master.ha...@gmail.com> --- I'm assuming they are qdockwidgets. as far as i know, qdockwidgets cant be turned into qmainwindows. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377389] background parser hogs memory and CPU while working with git
https://bugs.kde.org/show_bug.cgi?id=377389 --- Comment #3 from Ian Haber <master.ha...@gmail.com> --- Ah, that might do it. It does have to re-parse every file that changed though, which could end up being the equivalent of reparsing the entire project. There is an option that lets you turn down the number of processes it uses at a given time, so that might be an option for you to change it to one process, so it wont use all of your cpu. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377389] background parser hogs memory and CPU while working with git
https://bugs.kde.org/show_bug.cgi?id=377389 Ian Haber <master.ha...@gmail.com> changed: What|Removed |Added CC||master.ha...@gmail.com --- Comment #1 from Ian Haber <master.ha...@gmail.com> --- i've never seen it be a real issue with processing power, but i have a bunch of cores. The biggest issue i've seen with switching git branches is that it fucks up the parser and everything gets parsed wrong. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377027] KDevelop could feature a Designer UI
https://bugs.kde.org/show_bug.cgi?id=377027 Ian Haber <master.ha...@gmail.com> changed: What|Removed |Added CC||master.ha...@gmail.com --- Comment #3 from Ian Haber <master.ha...@gmail.com> --- I just created an external script to automatically run the file i want in designer by clicking on it in kdevelop. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377030] Request: find/replace special for row of replacement
https://bugs.kde.org/show_bug.cgi?id=377030 Ian Haber <master.ha...@gmail.com> changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377030] New: Request: find/replace special for row of replacement
https://bugs.kde.org/show_bug.cgi?id=377030 Bug ID: 377030 Summary: Request: find/replace special for row of replacement Product: kdevelop Version: 5.1.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: all editors Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com Target Milestone: --- It would be nice to have a special set of characters that when using the find/replace would automatically add in an incrementing number. This would be great for cases where you have a large list of values you want to find/replace where they need to be set equal to an incrementing number. One example would be having a structure that defines the parameters available in the comms, and then converting it to an enum that defines the list of structures. I'm sure there are plenty of other places where someone might want to do this. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377023] New: Hovering over folder in projects toolview toggles instead of opens
https://bugs.kde.org/show_bug.cgi?id=377023 Bug ID: 377023 Summary: Hovering over folder in projects toolview toggles instead of opens Product: kdevelop Version: 5.1.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: file tree Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com Target Milestone: --- If you drag a file from a location in the projects toolview, and then hover over a folder,that folder will toggle between open and closed. I would imagine that the intended behavior would be for it to always open the folder when hovering over it, but at the moment if the folder is already open, it will close the folder when you hover. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377017] New: creating a file generates extra 'part' files that require reload to remove
https://bugs.kde.org/show_bug.cgi?id=377017 Bug ID: 377017 Summary: creating a file generates extra 'part' files that require reload to remove Product: kdevelop Version: 5.1.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: file create Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com Target Milestone: --- When you create a file using the right click-> create file from the 'projects' toolview, it creates multiple '.part' files temporarily. This is fine, but once you do this, it requires a reload of the toolview to remove these temp files from the list. if you create 10 files, it will have added 30 files to the list. it is quite annoying to have to manually reload after doing this to remove the extra 20 files. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #26 from Ian Haber <master.ha...@gmail.com> --- Alright. I posted in the gdb bugtracking https://sourceware.org/bugzilla/show_bug.cgi?id=21192 hopefully they will fix it eventually. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #24 from Ian Haber <master.ha...@gmail.com> --- would it be possible to maybe have some sort of manually set variable that would be a prefix for member variables? a lot of us use a very specific member variable prefix, so if it starts with that prefix, chances are it is a member? it is also possible to determine if the variable was declared in the current scope by using 'info locals', right? so any variable not in 'info locals' would be a member? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #21 from Ian Haber <master.ha...@gmail.com> --- Created attachment 104158 --> https://bugs.kde.org/attachment.cgi?id=104158=edit Log file for the test case Here is the log file for the test case i created. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable
https://bugs.kde.org/show_bug.cgi?id=376595
--- Comment #20 from Ian Haber <master.ha...@gmail.com> ---
I have created a simple test program that causes the crash.
//main.cpp
int main(int argc, char* argv[])
{
QApplication applicationInstance(argc, argv);
testGDBCrash crasher;
if (crasher.exec() != QDialog::Accepted)
return 0;
return applicationInstance.exec();
}
//testGDBCrash.h
#ifndef TESTGDBCRASH_H
#define TESTGDBCRASH_H
#include
#include
class testGDBCrash : public QDialog
{
Q_OBJECT
public:
testGDBCrash(QWidget * parent=0);
Q_SLOT void TestCrash();
bool m_bInUpdate;
};
#endif // TESTGDBCRASH_H
//testGDBCrash.cpp
#include "testGDBCrash.h"
#include
#include
testGDBCrash::testGDBCrash(QWidget* parent):QDialog(parent)
{
resize(200,100);
QHBoxLayout * layout=new QHBoxLayout(this);
QPushButton * pb=new QPushButton("crash",this);
layout->addWidget(pb);
setLayout(layout);
show();
m_bInUpdate=false;
connect(pb,SIGNAL(clicked()),this,SLOT(TestCrash()));
}
void testGDBCrash::TestCrash()
{
if(m_bInUpdate)
return;
m_bInUpdate=false;
m_bInUpdate=true;
m_bInUpdate=false;
}
Steps to crash:
1. Run
2. put a breakpoint on line 18 of testGDBCrash.cpp (the if statement)
3. break on change for m_bInUpdate
4. Continue
5. Watch crash.
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #19 from Ian Haber <master.ha...@gmail.com> --- ran the test case, it does not give me the same behavior. i'm currently modifying it to see if i can reproduce the issue. As far as i can tell, the only differences between my current version of the test and my normal source is that the method i'm attempting to use this on is a slot... but in qt, pretty much everything is a slot or called by a slot. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #17 from Ian Haber <master.ha...@gmail.com> --- The patch does prevent the crash, although as you suggested, gdb is just sitting there hanging now. Messing with the gdb console outside of kdevelop led me to something interesting. if i use the command 'watch m_bInUpdate', when i attempt to continue, it will just say "current stack frame does not contain a variable named 'this'" and not do anything. If i use the command 'watch this.m_bInUpdate', it works as i would expect. Could it be that when kdevelop adds a watch for member variables it just uses 'watch '? That being said, if this were the case, i would expect that it would be causing issues for everyone. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #13 from Ian Haber <master.ha...@gmail.com> --- Created attachment 104134 --> https://bugs.kde.org/attachment.cgi?id=104134=edit Debug output for debugger Here is the output. my gdb version: GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #11 from Ian Haber <master.ha...@gmail.com> --- I get the crash regardless of how i set the breakpoint. i can set it in gdb or through kdevelop and both will crash. the only logging stuff i got was qt.core.logging: Ignoring malformed logging rule: 'kdevelop.debuggers.gdb.debug=true;kdevelop.debuggers.common.debug=true' at the start of the program and kdevelop.debuggers.common: "No environment group specified, looks like a broken configuration, please check run configuration 'xx'. Using default environment group." during the startup of my program. 'Breakpoint doesn't contain required location/expression data' is logged when i create the breakpoint. There is nothing after that before the backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #9 from Ian Haber <master.ha...@gmail.com> --- with those debug messages, i get the same backtrace as before, but i get QMetaObject::invokeMethod: No such method ExpandingTree::scrollTo(QModelIndex,QAbstractItemView::ScrollHint) Breakpoint doesn't contain required location/expression data before it. i would assume though that you could recreate this. it is 100% for me. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #7 from Ian Haber <master.ha...@gmail.com> --- if you need anything else from gdb, i still have it up and will get back to you on monday. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #6 from Ian Haber <master.ha...@gmail.com> --- here is the backtrace. it also looks like i got a message saying 'breakpoint doesn't contain required location/expression data'. maybe that has something to do with it Thread 1 "kdevelop" received signal SIGSEGV, Segmentation fault. 0x7fffb263a07e in KDevMI::MI::MICommand::markAsCompleted() () from /home/ian/kde-5/lib/x86_64-linux-gnu/plugins/kdevplatform/27/kdevgdb.so (gdb) bt #0 0x7fffb263a07e in KDevMI::MI::MICommand::markAsCompleted() () from /home/ian/kde-5/lib/x86_64-linux-gnu/plugins/kdevplatform/27/kdevgdb.so #1 0x7fffb263bd9d in KDevMI::MIDebugger::processLine(QByteArray const&) () from /home/ian/kde-5/lib/x86_64-linux-gnu/plugins/kdevplatform/27/kdevgdb.so #2 0x7fffb263b506 in KDevMI::MIDebugger::readyReadStandardOutput() () from /home/ian/kde-5/lib/x86_64-linux-gnu/plugins/kdevplatform/27/kdevgdb.so #3 0x7fffb263e308 in QtPrivate::FunctorCall<QtPrivate::IndexesList<>, QtPrivate::List<>, void, void (KDevMI::MIDebugger::*)()>::call(void (KDevMI::MIDebugger::*)(), KDevMI::MIDebugger*, void**) () from /home/ian/kde-5/lib/x86_64-linux-gnu/plugins/kdevplatform/27/kdevgdb.so #4 0x7fffb263e1ca in void QtPrivate::FunctionPointer::call<QtPrivate::List<>, void>(void (KDevMI::MIDebugger::*)(), KDevMI::MIDebugger*, void**) () from /home/ian/kde-5/lib/x86_64-linux-gnu/plugins/kdevplatform/27/kdevgdb.so #5 0x7fffb263ded1 in QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () from /home/ian/kde-5/lib/x86_64-linux-gnu/plugins/kdevplatform/27/kdevgdb.so #6 0x75d35baf in QtPrivate::QSlotObjectBase::call (a=0x7fffcfa0, r=0x6c72030, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124 #7 QMetaObject::activate (sender=sender@entry=0x6c72120, signalOffset=, local_signal_index=local_signal_index@entry=5, argv=argv@entry=0x0) at kernel/qobject.cpp:3698 #8 0x75d36537 in QMetaObject::activate (sender=sender@entry=0x6c72120, m=m@entry=0x75f4c400 , local_signal_index=local_signal_index@entry=5, argv=argv@entry=0x0) at kernel/qobject.cpp:3578 #9 0x75c34b63 in QProcess::readyReadStandardOutput (this=this@entry=0x6c72120) at .moc/moc_qprocess.cpp:266 ---Type to continue, or q to quit--- #10 0x75c3d0c2 in QProcessPrivate::tryReadFromChannel (this=0x6c72140, channel=0x6c72270) at io/qprocess.cpp:966 #11 0x75c3d540 in QProcessPrivate::_q_canReadStandardOutput (this=) at io/qprocess.cpp:977 #12 QProcess::qt_static_metacall (_o=, _c=, _id=, _a=0x7fffd1a0) at .moc/moc_qprocess.cpp:133 #13 0x75d35d2a in QMetaObject::activate (sender=sender@entry=0x6c72ec0, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fffd1a0) at kernel/qobject.cpp:3713 #14 0x75d36537 in QMetaObject::activate (sender=sender@entry=0x6c72ec0, m=m@entry=0x75f50780 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fffd1a0) at kernel/qobject.cpp:3578 #15 0x75db524e in QSocketNotifier::activated (this=this@entry=0x6c72ec0, _t1=82) at .moc/moc_qsocketnotifier.cpp:134 #16 0x75d421cb in QSocketNotifier::event (this=0x6c72ec0, e=) at kernel/qsocketnotifier.cpp:260 #17 0x765fa05c in QApplicationPrivate::notify_helper (this=this@entry=0x647190, receiver=receiver@entry=0x6c72ec0, e=e@entry=0x7fffd410) at kernel/qapplication.cpp:3716 #18 0x765ff516 in QApplication::notify (this=0x7fffd970, receiver=0x6c72ec0, e=0x7fffd410) at kernel/qapplication.cpp:3499 #19 0x75d0738b in QCoreApplication::notifyInternal (this=0x7fffd970, receiver=0x6c72ec0, event=event@entry=0x7fffd410) at kernel/qcoreapplication.cpp:965 #20 0x75d5dc95 in QCoreApplication::sendEvent (event=0x7fffd410, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:224 #21 socketNotifierSourceDispatch (source=0x7659a0) at kernel/qeventdispatcher_glib.cpp:101 #22 0x7fffee394197 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7fffee3943f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7fffee39449c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x75d5d7cf in QEventDispatcherGlib::processEvents (this=0x765850, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #26 0x75d04b4a in QEventLoop::exec (this=this@entry=0x7fffd620, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #27 0x75d0cbec in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1229 #28 0x0040e79e in main () -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #4 from Ian Haber <master.ha...@gmail.com> --- I get this build error when i attempt to build master. what module is KUrlRequester in that i'm assuming i need to add to the list of things to download and update. /home/ian/kdesrc/kdevelop/languages/plugins/custom-definesandincludes/compilerprovider/widget/compilerswidget.cpp:81:34: error: ‘textEdited’ is not a member of ‘KUrlRequester’ connect(m_ui->compilerPath, ::textEdited, this, ::compilerEdited); -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 376595] Kdevelop crashes on watch member variable
https://bugs.kde.org/show_bug.cgi?id=376595 --- Comment #2 from Ian Haber <master.ha...@gmail.com> --- so i've never been able to get a backtrace while using the appimage. I attempted to build source today, but it seems there are build errors in master at the moment. how do i set kdesrc-build to use branch 5.1 for kdevelop and kdevplatform? I attempted to modify the .kdesrc-buildrc and set it to use branch 5.1, but it attempts to use svn instead of git and then fails to update. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 376595] New: Kdevelop crashes on watch member variable
https://bugs.kde.org/show_bug.cgi?id=376595 Bug ID: 376595 Summary: Kdevelop crashes on watch member variable Product: kdevelop Version: 5.1.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: CPP Debugger Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com CC: niko.s...@gmail.com Target Milestone: --- Kdevelop crashes whenever a breakpoint on a watched variable is tripped (if the variable is a member variable). Local variables work as intended. Steps to reproduce: 1. Debug program 2. set Break on change for that variable 3. Run until that variable changes 4. watch crash. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 376554] New: Request: debug multiple executables
https://bugs.kde.org/show_bug.cgi?id=376554 Bug ID: 376554 Summary: Request: debug multiple executables Product: kdevelop Version: 5.1.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: CPP Debugger Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com CC: niko.s...@gmail.com Target Milestone: --- I would really love to see this feature implemented if it is possible. Debugging multiple executables at once is an incredibly useful feature. In eclipse it is possible to debug multiple executables at one time, but if you attempt to do that with kdev, it will just close down the first one you are debugging. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 375957] New: Split view keep current line
https://bugs.kde.org/show_bug.cgi?id=375957 Bug ID: 375957 Summary: Split view keep current line Product: kdevelop Version: 5.1.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: all editors Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com Target Milestone: --- It would be really nice if we using split view would set the created view to the same line as it started at before the split. For example, if i have a file at line 2k and then i use split view, it will create a new view at line 0 and keep the original one at 2k. It would be great if splitting in this scenario would have both at 2k to start. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 375547] New: Problems parser add exclusions
https://bugs.kde.org/show_bug.cgi?id=375547 Bug ID: 375547 Summary: Problems parser add exclusions Product: kdevelop Version: 5.1.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com Target Milestone: --- Is it possible to add regex exclusions to the problems section of the ui (for the parser and cpp check)? I have a pretty massive project with quite a few third party sections of code that i cant change. i would like to be able to show just my first party code's problems and ignore everything else. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 375543] New: Rename variable helper does not work in a few situations
https://bugs.kde.org/show_bug.cgi?id=375543
Bug ID: 375543
Summary: Rename variable helper does not work in a few
situations
Product: kdevelop
Version: 5.1.0
Platform: Appimage
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Language Support: CPP (Clang-based)
Assignee: kdevelop-bugs-n...@kde.org
Reporter: master.ha...@gmail.com
Target Milestone: ---
The rename variable helper has a few situations where it does not work
correctly:
1. if you rename a variable that has places highlighted for incorrect syntax,
the variable name will not be updated on those lines.
e.g.
int foo()
{
int bar;
bar.isValid();
//changing the name of bar will not update the name of bar in the second
line, because there is a syntax error
}
2. renaming a variable after changing the length of the line UP to the variable
name will cause variable name replacements to have extra text added to them
other than just the new variable name (sometimes including a few characters
after the variable name from the line that changed)
e.g.
int foo()
{
int bar=276;
bar=3;
}
changing bar to a QString and then renaming it will often lead to something
like this:
QString renamed=276;
renamed=273;
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 375304] New: Documentation helper shifted
https://bugs.kde.org/show_bug.cgi?id=375304 Bug ID: 375304 Summary: Documentation helper shifted Product: kdevelop Version: 5.1.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com Target Milestone: --- When hovering over a qt method, the popup gives documentation for the next method down in the documentation, not the correct one. For example, hovering over QTcpServer::listen will show documentation for QTcpServer::maxPendingConnections -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 375277] Some changes trigger unnecessary "update declaration" hint on constructor
https://bugs.kde.org/show_bug.cgi?id=375277
Ian Haber <master.ha...@gmail.com> changed:
What|Removed |Added
CC||master.ha...@gmail.com
--- Comment #1 from Ian Haber <master.ha...@gmail.com> ---
This also happens if you add another line of instantiation outside of the
brackets.
header: int bar;
cpp file:
class Foo:
bar(0)
{
}
adding the bar(0) will also do the update declaration signature thing.
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 375156] New: Variable information popup closes too quickly
https://bugs.kde.org/show_bug.cgi?id=375156 Bug ID: 375156 Summary: Variable information popup closes too quickly Product: kdevelop Version: 5.1.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: CPP Debugger Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com CC: niko.s...@gmail.com Target Milestone: --- Is it possible to increase the distance from the variable information popup on debugging before it hides? i consistently am attempting to increase the size of the popup to get information from the drop downs (it should probably do this automatically when expanding the tree), and the dialog will hide, forcing me to go through everything i was doing again. Also is it possible to get a scroll bar in this popup? sometimes it is actually impossible to get all the information i want from it because i cant expand it large enough on my screen. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 374967] pasting into .ui file indents the row
https://bugs.kde.org/show_bug.cgi?id=374967 Ian Haber <master.ha...@gmail.com> changed: What|Removed |Added Platform|Other |Appimage -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 374967] New: pasting into .ui file indents the row
https://bugs.kde.org/show_bug.cgi?id=374967 Bug ID: 374967 Summary: pasting into .ui file indents the row Product: kdevelop Version: 5.1.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: all editors Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com Target Milestone: --- when pasting text into a .ui file, the row being pasted into indents a level for no reason. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 369194] Background parser does not reparse other open files after changes
https://bugs.kde.org/show_bug.cgi?id=369194 --- Comment #7 from Ian Haber <master.ha...@gmail.com> --- Created attachment 103221 --> https://bugs.kde.org/attachment.cgi?id=103221=edit Parser bug video Added a video of the bug. In the first part, i show the correct case, what it is supposed to do. the second section i show the bug i'm having with the parser. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 374301] Code completion should offer variable first
https://bugs.kde.org/show_bug.cgi?id=374301 --- Comment #1 from Ian Haber <master.ha...@gmail.com> --- after offering the variable, it should probably proceed based on most likely by type of assign instead of by alphabetical order. QVariant data; QVariantList dataList=data.toList(); in this case, toList() should show up above toLine() because it makes more sense to assign QVariantList to QVariantList than QLine to QVariantList(this would even lead to a compile error) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 374301] New: Code completion should offer variable first
https://bugs.kde.org/show_bug.cgi?id=374301 Bug ID: 374301 Summary: Code completion should offer variable first Product: kdevelop Version: 5.0.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com Target Milestone: --- When using code completion, it should offer the variable before offering the variable's methods, regardless of what you using it for. QList values; int foo=values.at(0); if you hit the code completion at any point while typing 'values' before the '.', it will complete to 'values.count()'. i think it should probably always have the full variable name be at the top of the offered completion because hitting enter and accepting the first choice shouldnt ever require that you undo what you just did in order to get it right. If it offers the variable first, the worst that would happen is that you have to hit the dot to get the completion again. This is especially annoying because it seems to be ignoring a huge number of methods for QList, so it doesnt even realize that values.at() exists as a method. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 369418] Shortcuts for Kdevelop Handbook and What's this always overwrite setting
https://bugs.kde.org/show_bug.cgi?id=369418 --- Comment #1 from Ian Haber <master.ha...@gmail.com> --- if i were to take a look at fixing this, where should i look? i did some searching in the source code but i never could find anything that seemed related to this. Maybe it is just built into kde? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 373722] "Implement function" doesn't consider "using namespace"
https://bugs.kde.org/show_bug.cgi?id=373722 Ian Haber <master.ha...@gmail.com> changed: What|Removed |Added CC||master.ha...@gmail.com --- Comment #1 from Ian Haber <master.ha...@gmail.com> --- to tack on to this, if you add the namespace already to the name before the prompt comes up, it will rewrite the namespace again anyway, leaving you with foo::foo::bar instead of foo::bar. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372637] Build sometimes preventing quick open from working correctly
https://bugs.kde.org/show_bug.cgi?id=372637 --- Comment #2 from Ian Haber <master.ha...@gmail.com> --- no debug output in the terminal when it happens. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372637] New: Build sometimes preventing quick open from working correctly
https://bugs.kde.org/show_bug.cgi?id=372637 Bug ID: 372637 Summary: Build sometimes preventing quick open from working correctly Product: kdevelop Version: 5.0.2 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com Target Milestone: --- using the hotkey to open quick open file often doesnt work while building. Steps to reproduce: 1. start long build 2. use hotkey combination to open quick open dialog What happens: popup will show but then immediately disappear about 90% of the time. Expected results: popup should display and stay visible as normal when not compiling -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372599] New: code completion knows the answer but doesnt offer it
https://bugs.kde.org/show_bug.cgi?id=372599 Bug ID: 372599 Summary: code completion knows the answer but doesnt offer it Product: kdevelop Version: 5.0.2 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com Target Milestone: --- seeing a strange issue with the code completion, where it asks if i meant something, but doesnt offer it as a solution. Problem in semantic analysis "No member 'Foo' in 'Bar', did you mean 'foo'? Hint: 'foo' declared here See: double foo() in Bar.h it knows what i want, but it doesnt offer it as a solution under the alt menu. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 371645] "Program received signal SIGSEGV, Segmentation fault" while idle
https://bugs.kde.org/show_bug.cgi?id=371645 --- Comment #9 from Ian Haber <master.ha...@gmail.com> --- it does not seem to happen to me at all when using a built version of master instead of the appimage. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 371645] "Program received signal SIGSEGV, Segmentation fault" while idle
https://bugs.kde.org/show_bug.cgi?id=371645 Ian Haber <master.ha...@gmail.com> changed: What|Removed |Added CC||master.ha...@gmail.com --- Comment #8 from Ian Haber <master.ha...@gmail.com> --- i have noticed it 'randomly' crashing on my appimage as well. it seems to do it right after changing something in the code, but i cant get any backtrace, it seems there is a corrupt stack or something. It crashes at least once per hour at the moment, but it didnt do this before. sometimes though it doesnt even require me to change something, simply highlighting a section of code will crash it. Thread 1 "kdevelop" received signal SIGSEGV, Segmentation fault. [Switching to LWP 24312] 0x7c240d7d in ?? () (gdb) bt #0 0x7c240d7d in ?? () Backtrace stopped: Cannot access memory at address 0xf393b450 I also ran into an issue where the appimage wouldnt open and just instantly segfaults, deleting the cache didnt seem to change that, but rebooting did. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 371018] CPP parser responds very slow after user action
https://bugs.kde.org/show_bug.cgi?id=371018 --- Comment #14 from Ian Haber <master.ha...@gmail.com> --- the user defined delay works really well for my use case :). i fixed my problems altogether by just turning that timer up. i can now type whatever i want and get autocomplete on it before the reparse. This has sped up my workflow considerably (back to 4.7 speeds). Still having issues with templated qt classes though (BUG 371217) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 371326] New: Snippets not existent
https://bugs.kde.org/show_bug.cgi?id=371326 Bug ID: 371326 Summary: Snippets not existent Product: kdevelop Version: 5.0.2 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com Snippets do not seem to be available at the moment in the 5.0.2 app image. Reproducible: Always Steps to Reproduce: 1. open app image 2. look for snippets 3. Actual Results: will not find snippets toolview Expected Results: snippets toolview selectable. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 371217] Code completion for templated qt classes is incorrect
https://bugs.kde.org/show_bug.cgi?id=371217 Ian Haber <master.ha...@gmail.com> changed: What|Removed |Added Summary|Code completion for |Code completion for |templated classes is|templated qt classes is |incorrect |incorrect -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 371217] New: Code completion for templated classes is incorrect
https://bugs.kde.org/show_bug.cgi?id=371217
Bug ID: 371217
Summary: Code completion for templated classes is incorrect
Product: kdevelop
Version: 5.0.2
Platform: Appimage
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: code completion
Assignee: kdevelop-bugs-n...@kde.org
Reporter: master.ha...@gmail.com
it seems like all? templated code in qt (QList,QVector,QPair,QMap...) does not
get the correct responses from the code completion.
When getting code completion for one of these classes, it properly gives a list
of all functions, but it does not mark them as functions, same thing happens
for qpair's member variables(first,second). Instead the completion thinks they
are just text. hitting enter on one of them will just put in the text, but does
not act like a method normally acts(adding parenthesis, etc).
the detailed completion recognizes the functions and return types etc, but
still does not mark them with the function or variable type(gray or purple
symbol), and does the same thing as above.
Reproducible: Always
Steps to Reproduce:
1. declare any templated class on the stack in a function:
void foo()
{
QList bar;
}
2. attempt to use the variable and ask for code completion, detailed or not:
int i=bar. {ctrl+space)
Actual Results:
code completion will appear, but it thinks none of the methods are methods and
none of the variables are variables.
Expected Results:
The code completion should detect what are methods and variables and act as
such, like it does for every non-templated class( QDir, QString, QDateTime,
QFile...)
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 371018] CPP parser responds very slow after user action
https://bugs.kde.org/show_bug.cgi?id=371018 --- Comment #11 from Ian Haber <master.ha...@gmail.com> --- i just set the background parser delay to a much longer time, so that i can basically modify as much as a want and then stop typing after saving for reparse. it still seems to be slower on offering completion than v4. it still seems to wait about a half second before offering completion even when the parser isnt going to run for another 3 seconds. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 371018] CPP parser responds very slow after user action
https://bugs.kde.org/show_bug.cgi?id=371018 --- Comment #8 from Ian Haber <master.ha...@gmail.com> --- is the delay a set time or does it stop delaying as soon as the parser is done? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 371018] CPP parser responds very slow after user action
https://bugs.kde.org/show_bug.cgi?id=371018 --- Comment #4 from Ian Haber <master.ha...@gmail.com> --- i think the parser is required to update the problems maybe, but it shouldnt have to reparse the whole file just to get the completion for foo->bar(). if i'm adding to the file in such a way that should just do completion but shouldnt affect the rest of the file... it should just give me completion without reparsing. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 371018] CPP parser responds very slow after user action
https://bugs.kde.org/show_bug.cgi?id=371018 Ian Haber <master.ha...@gmail.com> changed: What|Removed |Added CC||master.ha...@gmail.com --- Comment #2 from Ian Haber <master.ha...@gmail.com> --- i have seen this issue as well.. my perspective on this is that maybe the background parser doesnt need to run as often? some things i change i would much prefer to have the quick completion over parsing. maybe a hotkey to manually call background parser for the current file and an option somewhere to reparse the whole project? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 371009] New: 5.0.2 breakpoints no longer visible in icon border
https://bugs.kde.org/show_bug.cgi?id=371009 Bug ID: 371009 Summary: 5.0.2 breakpoints no longer visible in icon border Product: kdevelop Version: 5.0.1 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com in 5.0.2, the breakpoints symbol is no longer visible in the icon border Reproducible: Always Steps to Reproduce: 1. click on icon border to add breakpoint 2. 3. Actual Results: breakpoint applied, but the symbol is not visible Expected Results: the breakpoint symbol should be visible. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 369194] Background parser does not reparse other open files after changes
https://bugs.kde.org/show_bug.cgi?id=369194 --- Comment #1 from Ian Haber <master.ha...@gmail.com> --- also related to this, the background parser will not reparse a file if it is not the current file when the parser decides to parse it. If you change a function in the header file or add to it and then quickly switch to the cpp file, it will not reparse that header file until you go back to it again. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 369418] New: Shortcuts for Kdevelop Handbook and What's this always overwrite setting
https://bugs.kde.org/show_bug.cgi?id=369418 Bug ID: 369418 Summary: Shortcuts for Kdevelop Handbook and What's this always overwrite setting Product: kdevelop Version: 5.0.1 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Profiles Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com i have f1 set to 'find uses' , and unset kdevelop handbook and what's this so that there isnt a conflict when using f1. Every time i restart kdevelop, those two unset settings go back to defaults. Reproducible: Always Steps to Reproduce: 1. Unset 'Kdevelop Handbook' and 'What's This?' in configure shortcuts 2. restart kdevelop 3. open configure shortcuts again Actual Results: Kdevelop Handbook setting is back at f1 and What's this? is back at Shift+f1. Expected Results: the two settings should still be unset -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 369403] No Autocomplete for calls to qt connect()
https://bugs.kde.org/show_bug.cgi?id=369403 Ian Haber <master.ha...@gmail.com> changed: What|Removed |Added Summary|QT connect calls do not |No Autocomplete for calls |have autocomplete |to qt connect() -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 369403] New: QT connect calls do not have autocomplete
https://bugs.kde.org/show_bug.cgi?id=369403 Bug ID: 369403 Summary: QT connect calls do not have autocomplete Product: kdevelop Version: 5.0.1 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com In KDevelop 4.7.3, when typing out a connect for signals/slots in qt, i would get an autocomplete for everything inside of the call, including inside of SIGNAL() and SLOT(). This does not seem to happen in 5.0.1. it seems to not understand what i'm looking for inside of the SIGNAL/SLOT macros. Reproducible: Always Steps to Reproduce: 1. Create a qobject with signals/slots: signals: void testSignal(double); slots: void testSlot(double); 2. type 'connect(this,SIGNAL()' 3.begin typing into the parenthesis in SIGNAL() 'test' Actual Results: It will only prompt for text completion, not context completion Expected Results: should prompt testSignal(double), and then on the slot, it should prompt testSlot(double), like it did in 4.7. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 369194] New: Background parser does not reparse other open files after changes
https://bugs.kde.org/show_bug.cgi?id=369194 Bug ID: 369194 Summary: Background parser does not reparse other open files after changes Product: kdevelop Version: 5.0.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com After changing a function previously marked private to public, the background parser did not reparse one of my open files which was attempting to call this function until after i made a change to that file. Reproducible: Always Steps to Reproduce: 1. create private function (private: void test();) in header file 2. attempt to call test from another open file(should highlight red for declared private) 3.change private function to public Actual Results: function will still be marked red on the file attempting to call it. Expected Results: background parser should reparse all open files and unmark that function call. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 369117] New: No progress bar for parsing project on open
https://bugs.kde.org/show_bug.cgi?id=369117 Bug ID: 369117 Summary: No progress bar for parsing project on open Product: kdevelop Version: 5.0.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language Support: CPP Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com on the new 5.0.1 app image, when i open kdevelop, it no longer gives a progress bar for the initial parsing like it did on 5.0.0. on the console i can see that it is still parsing though. Reproducible: Always Steps to Reproduce: 1. Open Kdevelop 2. 3. Actual Results: parsing active but no progress bar Expected Results: progress bar should be visible. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368704] New: Arguments for launch configuration does not escape special characters.
https://bugs.kde.org/show_bug.cgi?id=368704 Bug ID: 368704 Summary: Arguments for launch configuration does not escape special characters. Product: kdevelop Version: 5.0.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com Adding arguments with special characters in the launch configuration panel requires manual escaping. adding an unescaped '*' will cause kdevelop to return an error message saying "Failed to specify program to start" Reproducible: Always Steps to Reproduce: 1.Add any arguments containing '*' to launch configuration, i.e. --gtest_filter=* 2. Hit ok to save the launch 3. execute launch Actual Results: console returns error message: "*** Failed to specify program to start ***" Expected Results: launch executes correctly with the filter applied. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368108] New: Adapt signature helper doesnt keep virtual
https://bugs.kde.org/show_bug.cgi?id=368108
Bug ID: 368108
Summary: Adapt signature helper doesnt keep virtual
Product: kdevelop
Version: 5.0.0
Platform: Appimage
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Language Support: CPP (Clang-based)
Assignee: kdevelop-bugs-n...@kde.org
Reporter: master.ha...@gmail.com
using the adapt signature option after changing a function definition in the
cpp file removes the virtual keyword from the header file.
Reproducible: Always
Steps to Reproduce:
1. add function virtual void test(); to header file
2. add definition void test(){} to cpp file
3. add parameter to cpp file: void test(int val){}
4. use alt to bring up options, and use update declaration signature
Actual Results:
header file now has void test(int val);
Expected Results:
header file should have virtual void test(int val);
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 368107] New: Declaration helper/autocomplete not working
https://bugs.kde.org/show_bug.cgi?id=368107 Bug ID: 368107 Summary: Declaration helper/autocomplete not working Product: kdevelop Version: 5.0.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com When defining a variable, in 4.7.3 you could type out the variable name and assign any typed value to it, then hit alt+1 to automatically add the type before the name. This functionality does not work atm in v5.0 Reproducible: Always Steps to Reproduce: 1.type list=QList(); 2.hit alt to bring up semantic analysis 3. note that the option to declare list as type QList is not there Actual Results: semantic analysis just gives errors or does nothing at all Expected Results: semantic analysis should offer option to declare list as type QList, changing the line to QList list=QList(); -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 367973] New: View->Borders->show icon border not saving correctly
https://bugs.kde.org/show_bug.cgi?id=367973 Bug ID: 367973 Summary: View->Borders->show icon border not saving correctly Product: kdevelop Version: 5.0.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI: toplevel window Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com View->borders->show icon border is not saving correctly when switching between debug and code or when quitting/reopening kdevelop. Reproducible: Always Steps to Reproduce: 1.Set show icon border to true 2. switch back and forth between debug and code Actual Results: kdevelop will lose the setting for show icon border and you will have to set it again. sometimes it loses the setting in code mode, other times it loses it in debug mode. Expected Results: Show icon border value should be set and remembered. -- You are receiving this mail because: You are watching all bug changes.
