You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I did do a quick search about this problem here in the discussion and did see a few threads about similar problems, but I think my case might be s bit special, so I created this new thread anyway.
Basically, since I started using CDT for C++ development, I always noticed that the indexer behave ... strange sometimes.
It sometimes picks random functions und just always says that it can not find/resolve them, even tough if I click on it with Ctrl+Left-Click it jumps to the header defining it just fine.
Sometimes it also just generally marks everything as unresolved that comes from externally included headers for no reason (the header are still there, and I can open them fine using the Ctrl-Click method).
It changes between these behaviors mostly between IDE restarts, but sometimes it also just suddenly starts complaining about stuff, without doing more then en index rebuild or project refresh.
I now recently developed my own build system for java and c++ projects, and also made an Eclipse Plugin for it.
It just pushes a list of includes (headers) onto the CDT class path, which works perfectly fine, everything is recognized by the IDE and I can use autocomplete and open included headers.
But the indexer ... well ... it just got worse.
Its basically unusable right now, there are some rare times when it only complains about some of its "favorite functions" (the functions it always complained about, mostly memset, memfree and some std::chrono stuff)
I did reinstall eclipse a few times since I had this problem (aka since the first time using CDT).
Mostly during updates to newer versions.
I am currently on Eclipse 2024-12 4.34.0 and CDT 11.6, and it never changed during all those update times.
Maybe someone here can tell me if this is just a known issue with CDT or if there might be something wrong with my installation.
I cant think of any more things to try to fix this.
Using different toolchains does not change much by the way, no matter if I compile for linux, windows using mingw or SysGCC, its always the same.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I did do a quick search about this problem here in the discussion and did see a few threads about similar problems, but I think my case might be s bit special, so I created this new thread anyway.
Basically, since I started using CDT for C++ development, I always noticed that the indexer behave ... strange sometimes.
It sometimes picks random functions und just always says that it can not find/resolve them, even tough if I click on it with Ctrl+Left-Click it jumps to the header defining it just fine.
Sometimes it also just generally marks everything as unresolved that comes from externally included headers for no reason (the header are still there, and I can open them fine using the Ctrl-Click method).
It changes between these behaviors mostly between IDE restarts, but sometimes it also just suddenly starts complaining about stuff, without doing more then en index rebuild or project refresh.
I now recently developed my own build system for java and c++ projects, and also made an Eclipse Plugin for it.
It just pushes a list of includes (headers) onto the CDT class path, which works perfectly fine, everything is recognized by the IDE and I can use autocomplete and open included headers.
But the indexer ... well ... it just got worse.
Its basically unusable right now, there are some rare times when it only complains about some of its "favorite functions" (the functions it always complained about, mostly memset, memfree and some std::chrono stuff)
I did reinstall eclipse a few times since I had this problem (aka since the first time using CDT).
Mostly during updates to newer versions.
I am currently on Eclipse 2024-12 4.34.0 and CDT 11.6, and it never changed during all those update times.
Maybe someone here can tell me if this is just a known issue with CDT or if there might be something wrong with my installation.
I cant think of any more things to try to fix this.
Using different toolchains does not change much by the way, no matter if I compile for linux, windows using mingw or SysGCC, its always the same.
Beta Was this translation helpful? Give feedback.
All reactions