[kdevelop] [Bug 370993] KDevelop crashes shortly after startup

2016-10-20 Thread via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=370993

--- Comment #4 from andras.vuk...@gmail.com ---
(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.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 370993] KDevelop crashes shortly after startup

2016-10-18 Thread Kevin Funk via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=370993

--- Comment #3 from Kevin Funk  ---
Comment on attachment 101616
  --> https://bugs.kde.org/attachment.cgi?id=101616
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.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 370993] KDevelop crashes shortly after startup

2016-10-18 Thread via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=370993

--- Comment #2 from andras.vuk...@gmail.com ---
Created attachment 101616
  --> https://bugs.kde.org/attachment.cgi?id=101616=edit
GDB output together with first pause – signal SIGSEGV – continue

I’ve done as you suggested, and I’m attaching the output of GDB

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdevelop] [Bug 370993] KDevelop crashes shortly after startup

2016-10-17 Thread Kevin Funk via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=370993

Kevin Funk  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Kevin Funk  ---
[KCrash Handler]
#5  0x7f91de462f30 in  () at /usr/lib/libclang.so.3.8
#6  0x7f91de6a230c 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.