Qt Creator Clang Code Model problems collection
-
I had issue with autocompetion of inherited function parameters here:
https://forum.qt.io/topic/101748/autocompletion-doesn-t-suggest-function-parameters-inherited-from-parent-classAnd it is solved by turning off clang code model.
-
Hi @Maxxii,
thanks for adding your problem here. I think your specific problem can be turned in a report at bugreports.qt.io - as we already have a reproducible example. Would you mind doing that? (and adding a link here?)
Thanks!
-
https://forum.qt.io/topic/102198/many-incomprehensible-errors looks like another candidate...
-
https://forum.qt.io/topic/102272/using-qt-project-code-with-earlier-versions/10 also looks like a candidate
-
-
-
And another one: https://forum.qt.io/topic/102999/strange-variable-has-incomplete-type-and-forward-declaration-of-qapplication-issues
oh! I run into that as well, didn't think about turning off the code model as potential solution.
I ended up forwarding a class instance pointer several levels up in the hierarchy ....
This is stupid.
-
Hi @J.Hilk,
oh! I run into that as well, didn't think about turning off the code model as potential solution.
Well I don't think turning off the code model is a solution. But most of these problems collected here have in common, that Clang has parse problems in a header which then propagate in every file that is including the header.
Tracking down these problems, however, is a tedious task.
-
-
-
Hitting a similar issue in Qtcreatorv4.11.0 on linux x64 ubuntu18 lts with CMAKE and gcc or clang btw, the symbols parsing i.e. finding functions or type definitions does not work :
- does not work at all if not starting qtCreator in the actual CMAKE project source directory
- Always stops working regardless after a few minutes to about 1hours, requires a restart of Qtcreator after which it usually works again.
Make me hate trying to convince my colleagues to migrate from Eclipse to QtCreator, I was always telling them how much more usable and snappy QtCreator is but a bug like this is not a small bug and not a good look to my colleagues currently trying it.
Regards
-
Hi @rsacchettini,
Clang is a double-sided sword. If it works, it gives you fantastic insight in your code - but if not, you often have no idea why.
I'd recommend you nevertheless to start an own discussion topic here, we might be able to help you get it at least running. Can you at least work on a small example project?
Also note that the CMake integration is in flow currently, so there might be regressions in .0 releases. You might want to try the last stable or the next snapshot release.
Regards
Edit: Ah, you alread did: https://forum.qt.io/topic/111067/symbols-parsing-and-finding-stops-working-qtcreator-v4-11-0-cmake-on-linux-x64
-
When I just typed a few code in a c++ project,I got an error in the editor which was " no member named 'uint64_t' in namespace 'std' ".The code are listed here:
#include <iostream> #include <cstdint> using std::uint64_t
I didn't think it was the code made the issue.And I didn't know how to fix it until I found this topic.Actually,I solved the problem just by disabling Clang. It was really useful.
-
I have upgraded QtCreator to version 6. When I opened my project session clangd run out of memory and crashed my system. Sometimes it just crashes QtCreator:
[12437.692439] Out of memory: Killed process 56361 (clangd.main) total-vm: 1033980kb, anon-ess: 564302kb, shmem-rss: 0kb, UID: 1000, pgtables: 1360kb, oom_score_adj: 0
-
This post is deleted!
-
Helo, I have also this same problem with clang. I like this plugin, because it shows me future errors before I will compile program, but I noticed issue with NO auto completion in brackets, I want to autocomplete overloaded function in child class, but this is not working, and then I need spend time to open base class and copy all inputs from virtual function.
Turn it of plugin, helps fixing that issue, but now I cant use clang compilation warnings.
I do not need turn of auto closing brackets to autocomplete inputs in side brackets. Only clang code model is somehow blocking autocompletion. Maybe another plugin is colliding with clang and maybe finding another plugin will fix that issue, and will allow to use again clang?