https://bugs.kde.org/show_bug.cgi?id=362515
Sven Brauch changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=362515
--- Comment #7 from Sven Brauch ---
This should do, not 100% sure it is the correct fix. Let me know if you still
observe the crash.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=362515
--- Comment #5 from Sven Brauch ---
It looks a bit like the context gets deleted by something else. I wonder why
this started happening only now ...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=362515
--- Comment #4 from Francis Herne ---
More backtrace:
Thread 9 "KDevelop::Compl" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffa59be700 (LWP 13247)]
0x7fff88056020 in ?? ()
(gdb) bt full
#0 0x7fff88056020 in ?? (
https://bugs.kde.org/show_bug.cgi?id=362515
--- Comment #3 from Sven Brauch ---
Might be the same issue, I hit that two days ago myself:
Thread 12 "KDevelop::Compl" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffd10c6700 (LWP 11166)]
0x7fffc18177bc in
Python::Helper
https://bugs.kde.org/show_bug.cgi?id=362515
--- Comment #2 from Sven Brauch ---
Yes, different trace, but the same issue I think: the context passed to the
completion worker is null, and I wasn't aware that is possible. I wonder if
that changed recently, I need to investigate.
--
You are receiv
https://bugs.kde.org/show_bug.cgi?id=362515
--- Comment #1 from Francis Herne ---
Crashed again, backtrace looks a bit different:
Thread 9 "KDevelop::Compl" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffa3477700 (LWP 13580)]
KDevelop::DUChainBase::rangeInCurrentRevision
