https://bugs.kde.org/show_bug.cgi?id=370993
Kevin Funk <kf...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WAITINGFORINFO
--- Comment #1 from Kevin Funk <kf...@kde.org> ---
[KCrash Handler]
#5 0x00007f91de462f30 in () at /usr/lib/libclang.so.3.8
#6 0x00007f91de6a230c in () at /usr/lib/libclang.so.3.8
=> You're getting a SIGSEGV in libclang. This isn't necessarily critical,
libclang likely can recover from a SIGSEGV. You need to continue debugging in
order to find out the real issue for crashing.
If GDB is paused, with a backtrace like this, enter the following:
signal SIGSEGV
continue
This will make GDB re-raise the signal and continue debugging
(Note you might have to re-enter those commands multiple times, in case
KDevelop crashes again inside libclang.)
--
You are receiving this mail because:
You are watching all bug changes.
