https://bugs.kde.org/show_bug.cgi?id=427227
Francis Herne <m...@flherne.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |RESOLVED
CC| |m...@flherne.uk
Resolution|--- |DUPLICATE
--- Comment #1 from Francis Herne <m...@flherne.uk> ---
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.
