Summary: | KDevelop crashes shortly after startup | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | andras.vukics |
Component: | general | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED WAITINGFORINFO | ||
Severity: | crash | Keywords: | drkonqi |
Priority: | NOR | ||
Version: | 5.0.1 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | GDB output together with first pause – signal SIGSEGV – continue |
Description
andras.vukics
2016-10-17 08:58:16 UTC
[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.) Created attachment 101616 [details]
GDB output together with first pause – signal SIGSEGV – continue
I’ve done as you suggested, and I’m attaching the output of GDB
Comment on attachment 101616 [details]
GDB output together with first pause – signal SIGSEGV – continue
Sorry, forgot to tell you: please also install debug symbols for libclang.
Please generate a backtrace for both the first and the second SIGSEGV.
(In reply to Kevin Funk from comment #3) > Comment on attachment 101616 [details] > GDB output together with first pause – signal SIGSEGV – continue > > Sorry, forgot to tell you: please also install debug symbols for libclang. > > Please generate a backtrace for both the first and the second SIGSEGV. Sorry, but all the software I use comes from arch packages, and I couldn’t find the libclang debug symbols packaged for arch. |