[kdevelop] [Bug 427227] kdevelop parser crashes with SEGFAULT
https://bugs.kde.org/show_bug.cgi?id=427227 --- Comment #10 from Igor Kushnir --- (In reply to Mate Soos from comment #9) > Ah! Nce! Sorry, I was somehow convinced it must be my wrong setup > somehow that made the UI crash under GDB. That crash was making it *really* > hard for me to submit a backtrace, to be honest, so I'd be really happy if > it was fixed! Thanks for picking that up, that's great news! > > I added myself to the CC list of bug > https://bugs.kde.org/show_bug.cgi?id=427246 so I will be notified. Thanks > again! I am happy to help with traces, if needed. > > Cheers, > > Mate The GDB crash is already fixed in Qt, but not yet released. I've found it and added a comment with the fix description under Bug 427246 before I wrote my second comment here. So you won't be notified about that comment since you just subscribed to the issue :) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 427227] kdevelop parser crashes with SEGFAULT
https://bugs.kde.org/show_bug.cgi?id=427227 --- Comment #9 from Mate Soos --- Ah! Nce! Sorry, I was somehow convinced it must be my wrong setup somehow that made the UI crash under GDB. That crash was making it *really* hard for me to submit a backtrace, to be honest, so I'd be really happy if it was fixed! Thanks for picking that up, that's great news! I added myself to the CC list of bug https://bugs.kde.org/show_bug.cgi?id=427246 so I will be notified. Thanks again! I am happy to help with traces, if needed. Cheers, Mate -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 427227] kdevelop parser crashes with SEGFAULT
https://bugs.kde.org/show_bug.cgi?id=427227 --- Comment #8 from Igor Kushnir --- Mate, I commented about another non-Python bug - the GDB crash, which you and Francis have also discussed here. I've found the relevant Qt bug and the fix for the GDB crash. Described them in a comment to Bug 427246. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 427227] kdevelop parser crashes with SEGFAULT
https://bugs.kde.org/show_bug.cgi?id=427227 --- Comment #7 from Mate Soos --- Hey, Francis Herne has already figured it out thankfully and he has an upcoming fix in the next version. In the meanwhile, I disabled Python parsing and now it doesn't crash :) So this can be closed now. Thanks to all for the quick responses, Mate On Fri, Oct 2, 2020, 15:23 Igor Kushnir wrote: > https://bugs.kde.org/show_bug.cgi?id=427227 > > Igor Kushnir changed: > >What|Removed |Added > > > CC||igor...@gmail.com > > --- Comment #6 from Igor Kushnir --- > I logged *that* GDB crash as Bug 427246. Please comment under that bug if > you > have more information. Hopefully we can figure out why it happens... > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 427227] kdevelop parser crashes with SEGFAULT
https://bugs.kde.org/show_bug.cgi?id=427227 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com --- Comment #6 from Igor Kushnir --- I logged *that* GDB crash as Bug 427246. Please comment under that bug if you have more information. Hopefully we can figure out why it happens... -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 427227] kdevelop parser crashes with SEGFAULT
https://bugs.kde.org/show_bug.cgi?id=427227 --- Comment #5 from Mate Soos --- Thanks for getting back to me! I worked a lot to get the core to be dumped (oh, how I kinda hate/love systemd...), glad that it confirmed your suspicion. I also have now disabled the Python parser and indeed, it doesn't crash, works like charm :) Thanks so much, KDevelop is really great! BTW, I actually contributed with $$$ over the years, it really saves me a lot of time writing code. Looking forward to the new release! Cheers, Mate PS: Haha, 2:14AM now.. gotta work tomorrow :S -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 427227] kdevelop parser crashes with SEGFAULT
https://bugs.kde.org/show_bug.cgi?id=427227 --- Comment #4 from Francis Herne --- Backtrace confirms what I said above. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 427227] kdevelop parser crashes with SEGFAULT
https://bugs.kde.org/show_bug.cgi?id=427227 --- Comment #3 from Mate Soos --- Created attachment 132061 --> https://bugs.kde.org/attachment.cgi?id=132061=edit GDB backtrace Ah, I managed to fix the core issue, so now I am getting a core and can check it in GDB. Yay! I have to say, fighting with systemd was not fun. Anyway I have a backtrace. Sorry, no idea what generated the signal, so I dumped all threads' backtraces. Sorry, really late here now, so I won't add more. Dump is 245MB and probably contains pesonal information, so I'm not attaching it here. If you really need it, please email me at my login here (soos.m...@gmail.com) and I'll get back to you. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 427227] kdevelop parser crashes with SEGFAULT
https://bugs.kde.org/show_bug.cgi?id=427227 --- Comment #2 from Francis Herne --- Sorry, I forgot to include "uninstall `kdevelop-python`" or "disable the Python plugin in Configure KDevelop -> Plugins" as other workarounds. Obviously in that case you lose the Python support. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 427227] kdevelop parser crashes with SEGFAULT
https://bugs.kde.org/show_bug.cgi?id=427227 Francis Herne changed: What|Removed |Added Status|REPORTED|RESOLVED CC||m...@flherne.uk Resolution|--- |DUPLICATE --- Comment #1 from Francis Herne --- Thank you for the report. This is almost certainly the linked bug -- basically, I broke kdev-python in 5.6.0 for all CPython versions < 3.9... Sorry about that. We hope to release 5.6.1 soon. In the meantime, please either use a previous release (e.g. the 5.5.2 AppImage [1]) or compile with this patch applied [2]. [1] https://download.kde.org/stable/kdevelop/5.5.2/bin/linux/KDevelop-5.5.2-x86_64.AppImage [2] https://invent.kde.org/kdevelop/kdev-python/-/commit/172dc5138acf94d54215d630c2173d7f24ec97df.diff You're correct that the gdb crash is completely unrelated. I see the same thing (also on Arch), have tried debugging it in various ways and asked a number of people. It isn't due to a recent change in KDevelop, the same crash happens with compiled older versions. You can work around it by starting KDevelop normally and then using gdb --pid. If you have the slightest idea why *that* happens, it would be very helpful! *** This bug has been marked as a duplicate of bug 426292 *** -- You are receiving this mail because: You are watching all bug changes.
