[kdevelop] [Bug 371645] "Program received signal SIGSEGV, Segmentation fault" while idle

https://bugs.kde.org/show_bug.cgi?id=371645 red...@cox.net changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO

[kdevelop] [Bug 371645] "Program received signal SIGSEGV, Segmentation fault" while idle

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

[kdevelop] [Bug 371645] "Program received signal SIGSEGV, Segmentation fault" while idle

https://bugs.kde.org/show_bug.cgi?id=371645 --- Comment #12 from red...@cox.net --- Okay, looks I need to continue to try and reproduce the original issue. -- 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 #11 from Sven Brauch --- That is unrelated to the original issue and looks very much like a bug in libclang. It should be reported (and fixed) there. -- You are receiving this mail because: You are watching all bug

[kdevelop] [Bug 371645] "Program received signal SIGSEGV, Segmentation fault" while idle

https://bugs.kde.org/show_bug.cgi?id=371645 --- Comment #10 from red...@cox.net --- I have used the AppImage on a modern linux distro and do not have any problems. The code base is very small for that project though so the background parse does not run much (only a couple threads too). Back

[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 --- 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 changed: What|Removed |Added CC||master.ha...@gmail.com ---

[kdevelop] [Bug 371645] "Program received signal SIGSEGV, Segmentation fault" while idle

https://bugs.kde.org/show_bug.cgi?id=371645 --- Comment #7 from red...@cox.net --- No, I never changed the AppImage so it is definitely something that change on my end. I'll get to it eventually but in the meantime I was able to generate a segfault while parsing the Linux kernel source as test on

[kdevelop] [Bug 371645] "Program received signal SIGSEGV, Segmentation fault" while idle

https://bugs.kde.org/show_bug.cgi?id=371645 --- Comment #6 from Sven Brauch --- Did we break that between 5.0.1 and 5.0.2 ...? -- 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 #5 from red...@cox.net --- Something changed in my environment that prevents me from running the AppImage now so I think it will be best to close this as I can't reproduce it either. I will work on the issue eventually probably but it will

[kdevelop] [Bug 371645] "Program received signal SIGSEGV, Segmentation fault" while idle

https://bugs.kde.org/show_bug.cgi?id=371645 --- Comment #4 from red...@cox.net --- No, unfortunately this is not an open source project (I don't own the rights). I will get some open source projects and report back on if KDevelop still crashes with them. -- You are receiving this mail because:

[kdevelop] [Bug 371645] "Program received signal SIGSEGV, Segmentation fault" while idle

https://bugs.kde.org/show_bug.cgi?id=371645 --- Comment #3 from Sven Brauch --- Are the projects available somewhere so I could load them and see if I can reproduce the crash? -- 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 #2 from red...@cox.net --- I had custom cmake projects with C++ and python open. You are right in that it was not idle, but at the time I filed the bug I couldn't think of a better way to indicate the problem was not a result of direct user

[kdevelop] [Bug 371645] "Program received signal SIGSEGV, Segmentation fault" while idle

https://bugs.kde.org/show_bug.cgi?id=371645 Sven Brauch changed: What|Removed |Added CC||m...@svenbrauch.de ---

[kdevelop] [Bug 371645] "Program received signal SIGSEGV, Segmentation fault" while idle

https://bugs.kde.org/show_bug.cgi?id=371645 red...@cox.net changed: What|Removed |Added Platform|Balsam Professional |Appimage -- You are receiving this mail

[kdevelop] [Bug 371645] "Program received signal SIGSEGV, Segmentation fault" while idle

https://bugs.kde.org/show_bug.cgi?id=371645 red...@cox.net changed: What|Removed |Added Summary|"Program received signal|"Program received signal

[kdevelop] [Bug 371645] "Program received signal SIGSEGV, Segmentation" fault while idle

https://bugs.kde.org/show_bug.cgi?id=371645 red...@cox.net changed: What|Removed |Added Summary|Program received signal |"Program received signal