https://bugs.kde.org/show_bug.cgi?id=369631
Andrew Crouthamel changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=369631
Andrew Crouthamel changed:
What|Removed |Added
Keywords||triaged
--- Comment #13 from Andrew
https://bugs.kde.org/show_bug.cgi?id=369631
Krzysztof changed:
What|Removed |Added
CC||k...@limes.com.pl
--
You are
https://bugs.kde.org/show_bug.cgi?id=369631
Sven Brauch changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=369631
--- Comment #11 from Sven Brauch ---
Ah, in that case try
export QT_LOGGING_RULES="kdevelop.plugins.clang.debug=true"
then you should see processed files.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=369631
--- Comment #10 from Afief Halumi ---
@Kevin I don't recall there being a specific file, but I was a bit distracted
by things in my own code when it happened, so I'll take another look after the
new year's celebrations are over.
https://bugs.kde.org/show_bug.cgi?id=369631
--- Comment #9 from Sven Brauch ---
Or go up in the stack with the debugger and print it, e.g. the top context is
available almost everywhere and it has a url().
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=369631
--- Comment #8 from Kevin Funk ---
@Afief: Have a look at KDevelop's debug output in console. KDevelop usually
prints the files it currently attempts to parse to console.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=369631
--- Comment #7 from Afief Halumi ---
Is there a way to tell which file KDevelop was processing when it crashes? As
far as I understand it processes all my files in the background to support
better code navigation, so if the
https://bugs.kde.org/show_bug.cgi?id=369631
--- Comment #6 from Sven Brauch ---
Maybe you can figure out what file it crashes on and give us the part of it
that triggers the crash? That'd help a lot.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=369631
--- Comment #5 from Afief Halumi ---
Unfortunately it isn't a free/public, it's a rather convoluted more than 20
years old codebase in some dire need for refactoring.
If I had to guess I'd say the second bug somehow pollutes the
https://bugs.kde.org/show_bug.cgi?id=369631
--- Comment #4 from Sven Brauch ---
To me this crash looks quite different from the first one you posted. That
could be a bug. Is the project which you are working on public?
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=369631
--- Comment #3 from Afief Halumi ---
I seem to be getting the same crash multiple times today (may have something to
do wit the branch of the code I'm wroking with). This time it was a clean
startup which cleared the cache due to
https://bugs.kde.org/show_bug.cgi?id=369631
--- Comment #2 from Afief Halumi ---
The next startup gave me a popup about a possible cache corruption, so it fixed
itself.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=369631
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
---
15 matches
Mail list logo