https://bugs.kde.org/show_bug.cgi?id=363893
Bug ID: 363893
Summary: dynamic_cast error, type_info's (sic) should have
public visibility
Product: kdevelop
Version: git master
Platform: Compiled Sources
OS: OS X
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: kdevelop-bugs-n...@kde.org
Reporter: rjvber...@gmail.com
I'm not seeing these very often, so it took a while since I'v been asked to
file a bug report about them before I actually could:
```
Jun 3 13:34:20 Portia.local kdevelop[92832]: dynamic_cast error 1: Both of the
following type_info's should have public visibility. At least one of them is
hidden. N8KDevelop8IProblemE, 12ClangProblem.
Jun 3 13:35:11 Portia.local kdevelop[92832]: dynamic_cast error 1: Both of the
following type_info's should have public visibility. At least one of them is
hidden. N8KDevelop8IProblemE, 12ClangProblem.
```
These correspond to classes `KDevelop::IProblem` and `ClangProblem`.
Reproducible: Sometimes
Steps to Reproduce:
1. Start KDevelop
2. use it and keep an eye on /var/log/system.log
Actual Results:
Log entries about type_info visibility appear sporadically
Expected Results:
No such warnings.
In this case it appears to be a benign warning, but in the past they were
related to a dynamic_cast that actually failed.
I do need to point out that the clang parser keeps hogging the main thread on
OS X, leading to frequent and extremely annoying UI freezes when editing code.
A link between a (compensated) dynamic_cast failure of a ClangProblem and
"falling back to solving it on the main thread" doesn't seem completely
farfetched.
--
You are receiving this mail because:
You are watching all bug changes.
