https://bugs.kde.org/show_bug.cgi?id=382771
--- Comment #15 from Kevin Funk ---
> When I'm done with this, perhaps I should write a blog post about using
> KDevelop to work on gcc.
That'd be very much appreciated, make sure to notify us on e.g.
kdeve...@kde.org or #kdevelop on Freenode. Thank
https://bugs.kde.org/show_bug.cgi?id=382771
--- Comment #14 from Daniel Santos ---
(In reply to Kevin Funk from comment #13)
> The only sane way to fix this is to ignore the whole testsuite/ folder by
> placing an empty .kdev_ignore in it (this will make KDevelop's background
> parser ignore ever
https://bugs.kde.org/show_bug.cgi?id=382771
--- Comment #13 from Kevin Funk ---
The only sane way to fix this is to ignore the whole testsuite/ folder by
placing an empty .kdev_ignore in it (this will make KDevelop's background
parser ignore everything below it).
Please try and report back!
--
https://bugs.kde.org/show_bug.cgi?id=382771
--- Comment #12 from Kevin Funk ---
> "/home/daniel/proj/sys/gcc/git/gcc/testsuite/g++.dg/parse/stack1.C"
Yes, I feared something like this. KDevelop is attempting to parse one of GCC's
unit tests. These are usually regressions tests for very bad compi
https://bugs.kde.org/show_bug.cgi?id=382771
--- Comment #11 from Daniel Santos ---
Well here you go, this is at least one parse fail for upstream. This was w/o
gdb so I don't have a backtrace, but I'll guess that clang had a stack overflow
like gcc did prior to fixing it. I'm still not certain
https://bugs.kde.org/show_bug.cgi?id=382771
--- Comment #10 from Daniel Santos ---
(In reply to Kevin Funk from comment #9)
> Please try starting KDevelop in the terminal like this:
> QT_LOGGING_RULES="kdev*=true" kdevelop --ps
Interesting, I tried running
QT_LOGGING_RULES="kdev*=true" gdb -
https://bugs.kde.org/show_bug.cgi?id=382771
Kevin Funk changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=382771
--- Comment #8 from Daniel Santos ---
Ping.
(In reply to Kevin Funk from comment #4)
> - Could you try to figure out which file KDevelop crashes on? The last lines
> of the debug output of kdevelop should tell you what it is currently parsing.
By the
https://bugs.kde.org/show_bug.cgi?id=382771
--- Comment #7 from Daniel Santos ---
Created attachment 106964
--> https://bugs.kde.org/attachment.cgi?id=106964&action=edit
unending stack trace
(In reply to Kevin Funk from comment #4)
> - Could you try to figure out which file KDevelop crashes on
https://bugs.kde.org/show_bug.cgi?id=382771
Daniel Santos changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=382771
--- Comment #5 from Daniel Santos ---
(In reply to Kevin Funk from comment #4)
> I can't find a bug report with a similar backtrace from Upstream.
>
> Could you provide a bit more information?
> - Which project are you working on? Can you share?
This i
https://bugs.kde.org/show_bug.cgi?id=382771
--- Comment #4 from Kevin Funk ---
I can't find a bug report with a similar backtrace from Upstream.
Could you provide a bit more information?
- Which project are you working on? Can you share?
- Could you try to figure out which file KDevelop crashes
https://bugs.kde.org/show_bug.cgi?id=382771
Kevin Funk changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=382771
--- Comment #3 from Daniel Santos ---
Created attachment 106881
--> https://bugs.kde.org/attachment.cgi?id=106881&action=edit
emerge --info on all deps of kdevelop
If you need to know anything else about my environment, I've included the
emerge --inf
https://bugs.kde.org/show_bug.cgi?id=382771
--- Comment #2 from Daniel Santos ---
Created attachment 106880
--> https://bugs.kde.org/attachment.cgi?id=106880&action=edit
.kdev4/gcc-git.kdev4
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=382771
--- Comment #1 from Daniel Santos ---
Created attachment 106879
--> https://bugs.kde.org/attachment.cgi?id=106879&action=edit
project file
--
You are receiving this mail because:
You are watching all bug changes.
16 matches
Mail list logo