[kdevelop] [Bug 379854] kdevelop crashes after closing splitview

2021-01-15 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=379854 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO

[kdevelop] [Bug 379854] kdevelop crashes after closing splitview

2020-12-31 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=379854 --- Comment #16 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular

[kdevelop] [Bug 379854] kdevelop crashes after closing splitview

2020-12-16 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=379854 Justin Zobel changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|---

[kdevelop] [Bug 379854] kdevelop crashes after closing splitview

2017-06-01 Thread Ian Haber
https://bugs.kde.org/show_bug.cgi?id=379854 --- Comment #14 from Ian Haber --- 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

2017-06-01 Thread Milian Wolff
https://bugs.kde.org/show_bug.cgi?id=379854 Milian Wolff changed: What|Removed |Added Status|NEEDSINFO |UNCONFIRMED

[kdevelop] [Bug 379854] kdevelop crashes after closing splitview

2017-06-01 Thread Milian Wolff
https://bugs.kde.org/show_bug.cgi?id=379854 --- Comment #12 from Milian Wolff --- Hm ok DocumentController::activeDocument actually contains a dynamic_cast, but I wonder how that can crash here. I think we'll need to valgrind this - which is probably not possible with the

[kdevelop] [Bug 379854] kdevelop crashes after closing splitview

2017-05-31 Thread Ian Haber
https://bugs.kde.org/show_bug.cgi?id=379854 --- Comment #11 from Ian Haber --- 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,

[kdevelop] [Bug 379854] kdevelop crashes after closing splitview

2017-05-31 Thread Milian Wolff
https://bugs.kde.org/show_bug.cgi?id=379854 --- Comment #10 from Milian Wolff --- is it thread 1 that crashed? gdb should tell you that on the segfault. I wonder, b/c the function you point to does not contain a dynamic_cast, so i really wonder what is going on there... I also

[kdevelop] [Bug 379854] kdevelop crashes after closing splitview

2017-05-30 Thread Ian Haber
https://bugs.kde.org/show_bug.cgi?id=379854 --- Comment #9 from Ian Haber --- 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

[kdevelop] [Bug 379854] kdevelop crashes after closing splitview

2017-05-30 Thread Ian Haber
https://bugs.kde.org/show_bug.cgi?id=379854 --- Comment #8 from Ian Haber --- 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

[kdevelop] [Bug 379854] kdevelop crashes after closing splitview

2017-05-30 Thread Milian Wolff
https://bugs.kde.org/show_bug.cgi?id=379854 --- Comment #7 from Milian Wolff --- try the nightly build: http://kfunk.ddns.net:8080/job/kdevelop-appimage-centos/lastSuccessfulBuild/artifact/KDevelop-git-x86_64.AppImage launch it normally, then attach GDB, then reproduce the

[kdevelop] [Bug 379854] kdevelop crashes after closing splitview

2017-05-30 Thread Ian Haber
https://bugs.kde.org/show_bug.cgi?id=379854 --- Comment #6 from Ian Haber --- 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

[kdevelop] [Bug 379854] kdevelop crashes after closing splitview

2017-05-30 Thread Ian Haber
https://bugs.kde.org/show_bug.cgi?id=379854 --- Comment #5 from Ian Haber --- 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

2017-05-30 Thread Milian Wolff
https://bugs.kde.org/show_bug.cgi?id=379854 --- Comment #4 from Milian Wolff --- try attaching to the kdevelop process with gdb after launching it through appimage, does this work? -- You are receiving this mail because: You are watching all bug changes.

[kdevelop] [Bug 379854] kdevelop crashes after closing splitview

2017-05-30 Thread Ian Haber
https://bugs.kde.org/show_bug.cgi?id=379854 --- Comment #3 from Ian Haber --- 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

[kdevelop] [Bug 379854] kdevelop crashes after closing splitview

2017-05-30 Thread Milian Wolff
https://bugs.kde.org/show_bug.cgi?id=379854 Milian Wolff changed: What|Removed |Added Resolution|--- |BACKTRACE

[kdevelop] [Bug 379854] kdevelop crashes after closing splitview

2017-05-15 Thread Ian Haber
https://bugs.kde.org/show_bug.cgi?id=379854 --- Comment #1 from Ian Haber --- 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.