[kate] [Bug 356473] Crashes after trying to open c/c++ files

[Dominik Haumann via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356473

Dominik Haumann  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #4 from Dominik Haumann  ---
is fixed meanwhile.

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

[kate] [Bug 356473] Crashes after trying to open c/c++ files

[Dominik Haumann via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356473

Dominik Haumann  changed:

   What|Removed |Added

 CC||manuel_songo...@yahoo.it

--- Comment #3 from Dominik Haumann  ---
*** Bug 359754 has been marked as a duplicate of this bug. ***

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

[kate] [Bug 356473] Crashes after trying to open c/c++ files

[Matheus via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356473

--- Comment #2 from Matheus  ---
As I'm running on ubuntu, I've installed kdevelop throught apt-get
install kdevelop. I have allready tryied to run apt-get remove --purge
kdevelop* and reinstall it, install using the .deb package and I'm
allways getting the same error. Now I discovered that this only
happens with a single file Isn't it quite interesting?  I guess I
mentioned in the report that it happens with all cpp codes, but
testing it now I didn't had any issue. The code was actually that
large, about 40 lines of code. I is a test code and don't do anything
because its totally incomplete and buggy. It's attached to this
reply(named generator.cpp). Try yourself and see if you can open it.

2015-12-10 14:02 GMT-02:00 Milian Wolff via KDE Bugzilla
:
> https://bugs.kde.org/show_bug.cgi?id=356473
>
> Milian Wolff  changed:
>
>What|Removed |Added
> 
>  Status|UNCONFIRMED |NEEDSINFO
> Version|4.7.1   |unspecified
> Product|kdevelop|kate
>  Resolution|--- |WAITINGFORINFO
>Assignee|kdevelop-bugs-n...@kde.org  |kwrite-bugs-n...@kde.org
>   Component|general |part
>
> --- Comment #1 from Milian Wolff  ---
> Crash in KSycocaEntry, this means your environment is probably misconfigured.
> Do you compile KDevelop yourself? If so, where do you install it to? Do you
> setup KDEDIRS properly, and run kbuildsycoca4?
>
> Furthermore, can you get more debug symbols for katepart, including file/line
> numbers?
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[kate] [Bug 356473] Crashes after trying to open c/c++ files

[Milian Wolff via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356473

Milian Wolff  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
Version|4.7.1   |unspecified
Product|kdevelop|kate
 Resolution|--- |WAITINGFORINFO
   Assignee|kdevelop-bugs-n...@kde.org  |kwrite-bugs-n...@kde.org
  Component|general |part

--- Comment #1 from Milian Wolff  ---
Crash in KSycocaEntry, this means your environment is probably misconfigured.
Do you compile KDevelop yourself? If so, where do you install it to? Do you
setup KDEDIRS properly, and run kbuildsycoca4?

Furthermore, can you get more debug symbols for katepart, including file/line
numbers?

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