https://bugs.kde.org/show_bug.cgi?id=374097
--- Comment #22 from Jonathan Verner ---
I definitely will. Unfortunately, I currently don't have a kde5 devel
environment. Eventually I plan to setup a devel environment and compile
kdevelop from sources. Until then, though, I'll need to wait for a new
https://bugs.kde.org/show_bug.cgi?id=374097
--- Comment #21 from Sven Brauch ---
I hope this actually fixes the issue for you, I'm not 100% sure. Let me know
whether it still happens if you get a chance to test.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=374097
--- Comment #20 from Jonathan Verner ---
Thanks for your work!!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=374097
Sven Brauch changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/kde
|
https://bugs.kde.org/show_bug.cgi?id=374097
--- Comment #18 from Sven Brauch ---
Git commit 4cf23720b123dee3b4ad85957ed165d23e37e1e7 by Sven Brauch.
Committed on 14/01/2017 at 12:15.
Pushed by brauch into branch '5.1'.
container types: do not write lock when calling addContentType()
This should
https://bugs.kde.org/show_bug.cgi?id=374097
--- Comment #17 from Sven Brauch ---
The project does not seem to be marked as public there, or is it?
Another option is to just send me a tar archive (to mail at svenbrauch.de), I
can forward it to the 1-2 other involved developers, then you don't nee
https://bugs.kde.org/show_bug.cgi?id=374097
--- Comment #16 from Jonathan Verner ---
Well, the project is semi-public (website of our department, I am not sure
about my security skills and don't want people to go looking for bugs and then
doing bad stuff with the website :-)). Anyway, for the tim
https://bugs.kde.org/show_bug.cgi?id=374097
--- Comment #15 from Sven Brauch ---
The highlighting does look odd, though. The parameter "cls" doesn't have the
same colour as the uses. That might be related.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=374097
--- Comment #14 from Sven Brauch ---
Hmm, we are still not able to reproduce this. Really strange ... is the project
the file is from public? Maybe it only happens when the whole project is
loaded?
--
You are receiving this mail because:
You are watch
https://bugs.kde.org/show_bug.cgi?id=374097
--- Comment #13 from Jonathan Verner ---
I can also reproduce the crash with the 5.1 beta release... It gives me a
similar backtrace:
#0 0x7fffa8f3 in
Python::Helper::declarationForName(KDevelop::QualifiedIdentifier const&,
KDevelop::RangeInRe
https://bugs.kde.org/show_bug.cgi?id=374097
--- Comment #12 from Jonathan Verner ---
Hmm, it seems the file needs to be opened in a larger project (so far, I didn't
encounter the crash when editing just the file with no project open). The
particular file comes from a simple django project. Howeve
https://bugs.kde.org/show_bug.cgi?id=374097
--- Comment #11 from Sven Brauch ---
Thanks for the trace, that looks somewhat useful. It seems remotely familiar,
but I'm not sure what causes the crash ... I'll try to reproduce it with the
file you provided.
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=374097
--- Comment #10 from Jonathan Verner ---
Created attachment 103022
--> https://bugs.kde.org/attachment.cgi?id=103022&action=edit
Modified AppRun script to run kdevelop in gdb
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=374097
--- Comment #9 from Jonathan Verner ---
(In reply to Sven Brauch from comment #8)
> You can rename the AppImage to .iso, then unpack it with ark. In the
> "AppRun" script, in the last line, put "gdb kdevelop" instead of "kdevelop",
> then run that scrip
https://bugs.kde.org/show_bug.cgi?id=374097
--- Comment #8 from Sven Brauch ---
You can rename the AppImage to .iso, then unpack it with ark. In the "AppRun"
script, in the last line, put "gdb kdevelop" instead of "kdevelop", then run
that script; then it will run in gdb and you should be able to
https://bugs.kde.org/show_bug.cgi?id=374097
Jonathan Verner changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=374097
--- Comment #6 from Sven Brauch ---
Clearing .cache is a major performance impact with KDevelop, you'll have to
wait for ages until it rebuilds its code representation cache ... just so you
know ;)
--
You are receiving this mail because:
You are watch
https://bugs.kde.org/show_bug.cgi?id=374097
--- Comment #5 from Jonathan Verner ---
(In reply to Jonathan Verner from comment #4)
> ...
> and starting kdevelop again fixed it.
ignore that last line, it doesn't make grammatical sense with the previous
lines and I forgot to delete it.
--
You ar
https://bugs.kde.org/show_bug.cgi?id=374097
--- Comment #4 from Jonathan Verner ---
> Rebooting doesn't clear .cache
In my setup it does :-)
> but kdevelop does it at some point after a crash.
That might have happened too :-)
> I'll close this, please reopen if it happens again.
I just hit
https://bugs.kde.org/show_bug.cgi?id=374097
Sven Brauch changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=374097
--- Comment #2 from Jonathan Verner ---
> Can you reproduce the issue you describe every time?
> Can you still reproduce it > after closing kdevelop and removing
> ~/.cache/kdevduchain?
That is weird. It crashed on me reliably every time. But now it
https://bugs.kde.org/show_bug.cgi?id=374097
--- Comment #1 from Sven Brauch ---
Thanks for the precise report. I can't reproduce it though ... no crash here. I
just notice it's very laggy with code style checking enabled (really need to
fix that).
Can you reproduce the issue you describe every t
22 matches
Mail list logo
