https://bugs.kde.org/show_bug.cgi?id=386720
Milian Wolff <m...@milianw.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |CONFIRMED
--- Comment #8 from Milian Wolff <m...@milianw.de> ---
Reproduced it now in a project of mine. There, the reason is that we get *tons*
of problems due to broken include paths, which then trigger lots and lots of
"include file not found". If that happens deep in the include stack, the
problem also have tons of child diagnostics (i.e. "included from ..."). These
child diagnostics have only a cursor, not a range, and then the hack to compute
a range out of it seems to be quite slow:
auto nextLocation = clang_getLocation(unit, file, line, column + 100);
--
You are receiving this mail because:
You are watching all bug changes.
