[kdevelop] [Bug 376955] Segmentation fault when opening project configuration

2017-03-30 Thread Francis Herne
https://bugs.kde.org/show_bug.cgi?id=376955 Francis Herne changed: What|Removed |Added Resolution|--- |DUPLICATE

[kdevelop] [Bug 376955] Segmentation fault when opening project configuration

2017-02-26 Thread Sven Brauch
https://bugs.kde.org/show_bug.cgi?id=376955 Sven Brauch changed: What|Removed |Added Ever confirmed|0 |1

[kdevelop] [Bug 376955] Segmentation fault when opening project configuration

2017-02-26 Thread Richard Gladman
https://bugs.kde.org/show_bug.cgi?id=376955 --- Comment #4 from Richard Gladman --- $ > gdb ./KDevelop-5.0.80-x86_64.AppImage GNU gdb (GDB; openSUSE Tumbleweed) 7.11.1 Copyright (C) 2016 Free Software Foundation, Inc.

[kdevelop] [Bug 376955] Segmentation fault when opening project configuration

2017-02-26 Thread Sven Brauch
https://bugs.kde.org/show_bug.cgi?id=376955 --- Comment #3 from Sven Brauch --- Ah ok, just run kdevelop in gdb by hand: # gdb kdevelop > run Then when it crashes, generate the backtrace by typing > thread apply all bt Greetings, Sven -- You are receiving this mail

[kdevelop] [Bug 376955] Segmentation fault when opening project configuration

2017-02-26 Thread Richard Gladman
https://bugs.kde.org/show_bug.cgi?id=376955 --- Comment #2 from Richard Gladman --- (In reply to Sven Brauch from comment #1) > Backtrace please. I'm not sure how. Often when an application crashes, an error handler pops up that helps generate a back trace

[kdevelop] [Bug 376955] Segmentation fault when opening project configuration

2017-02-26 Thread Sven Brauch
https://bugs.kde.org/show_bug.cgi?id=376955 Sven Brauch changed: What|Removed |Added Resolution|--- |WAITINGFORINFO