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.
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!