Eclipse CDT shows semantic errors, but compilation is ok

Question

I have installed Eclipse Indigo for C/C++ Linux developers on Ubuntu 10.04 x86.

When I use common predefined macro __BASE_FILE__ Eclipse says Symbol '__BASE_FILE__' could not be resolved, but compilation is OK. I have to use it so often in my code and Eclipse fills my screen with red lines and bug icons :)

How can I fix this?

Perhaps this will help some: [see here](http://stackoverflow.com/questions/8204245/eclipse-cdt-gtkmm-could-not-be-resolved-but-compiles-and-runs) — Adam Miller, May 04 '12 at 06:47

score 25 · Answer 1 · answered Apr 09 '12 at 23:13

25

Not sure if this addresses your specific problem, but I also had semantic errors. They just came out of the blue after having a working project.

Anyway, I fixed it with a single option in workspace settings by setting: "Build configuration for indexer: Use active build configuration"

The other option was "Use the build configuration specified in the project's indexer settings" and this is the one that wasn't working. I think it may have been corrupted after an eclipse crash.

answered Apr 09 '12 at 23:13

taloft

251
3
3

2

Seems to be it is bug of the static analyzer, not the indexer. In any case it isn't working for me. Thanks for your efforts. – fasked Apr 10 '12 at 17:46
1

Hi talot, I couldn't find out how to access to the "workspace setting"> "Build configuration for indexer: Use active build configuration". Could you please tell me where to find it. thanks – ahmed_khan_89 Dec 04 '14 at 16:03
4

@ahmed_khan_89 Window -> Preferences -> C/C++ -> Indexer – Paolo M Feb 10 '15 at 10:36
In my case, the other option was selected "Use project indexer setting" or something like that. But in my project settings, the box for "enable project specific indexer settings" was disabled anyway. So it should have picked up the global/active build configuration automatically. But explicitly switching to active build configuration made the pesky red squiggles go away! – shikhanshu Mar 21 '17 at 21:02

score 24 · Answer 2 · answered Aug 26 '13 at 15:39

24

Window -> Preferences -> C/C++ -> Code Analysis -> Syntax and Semantic Errors: OFF

This won't solve the cause of the problem but at least will stop the false errors from being shown.

answered Aug 26 '13 at 15:39

WindRider

11,958
6
50
57

3

I almost downvote your answer because it is not the right solution, but after trying around, yours is the best solution. I have a lot of errors reported by calling boost and quince functions, and those errors drive me crazy to the point I have to turn off Eclipse error analysis feature. – Anh Tuan Jul 22 '15 at 04:45
2

I downvoted your answer, but if after this, the autocompletion works, I will upvote it. After YEARS, this problem is still annoying me and every time it takes long time to make it work, by performing random clean, build, close project, build index, fresh files etc – HAL9000 May 12 '16 at 21:21
1

This truly does seem to be the only fix. Years later I am in CCS (based on eclipse) and it was harder to find, but it is the only thing that gets them to go away – Plater May 10 '19 at 16:31

score 7 · Answer 3 · edited Aug 03 '16 at 08:35

7

The simplest solution is to reset the indexer:

Window / Preferences / C/C++ / Indexer.
uncheck "Enable indexer" ->>OK
rebuild all, may show lots of errors
check "Enable indexer" ->>OK
rebuild all

This error can be produced by forced closing of eclipse by power failure.

edited Aug 03 '16 at 08:35

Khlorghaal

230
2
11

answered Jun 12 '14 at 11:16

Zazun

69
1
1

There's more possible causes than power failure. This happened to me when I pulled my project repo onto a machine with a newer version of eclipse. – Khlorghaal Aug 03 '16 at 07:21
2

This worked. But next time I'll try rt-click on project, index, rebuild. – PaulQ Dec 01 '17 at 23:36

score 6 · Answer 4 · answered Feb 05 '16 at 18:57

6

You need to rebuild the index of your project.

Right-click on the project, then Index->Rebuild.

answered Feb 05 '16 at 18:57

mczraf

161
1
2

score 6 · Answer 5 · answered Sep 06 '16 at 14:16

6

Deleting the .metadata folder , and then Import project .

This way is OK!

answered Sep 06 '16 at 14:16

Tanghuihua

61
1
1

score 3 · Answer 6 · answered Dec 07 '12 at 13:39

IMO the correct solution is to define the symbol in Project -> Properties->C/C++ General -> Paths and Symbols -> Symbols tab. Since you can assume the symbol will always be supplied by the compiler, you just tell Eclipse to consider it defined.

I had the same problem just recently, where Eclipse complained about undefined macro, that i always supply using -D<MACRO_NAME> compiler option.

score 3 · Answer 7 · answered Feb 16 '14 at 18:05

I think it has something to do with the workspace/.metadata. I had the problem of semantic errors reported but Hello World compiles and runs. I deleted the project, created another one, same error reporting. Reinstalled CDT, same thing. Deleted the workspace, shut down Eclipse, restarted, created new hello world, same thing. Deleted the workspace again, shut down Eclipse again, this time noticed that Eclipse had recreated the workspace folder during shutdown when it couldn't find it. Deleted the workspace with Eclipse shut down. Restarted Eclipse, created HW project, errors show for about a second and then gone. Deleted project, created another one, errors show for a sec, then poof. If you actually had projects in your workspace (mine was a clean install), I bet that you could just delete the .metadata folder within the workspace, and it would fix it.

this worked for me. Delete the entire .metadata folder (which is at the root of the workspace), and restart eclipse. file->import to re-add the existing projects of course, i didn't have anything non-trivial set up in the workspace. — some bits flipped, Jun 03 '14 at 17:25
worked here as well. Just after reimporting the projects, everything was reported as an error which made my heart sink, but a few cycles of the cpu later, all is good. — mallardz, Sep 15 '14 at 17:48

ondrisko · Answer 8 · 2011-11-16T08:47:06.307

3

Updated: You have to add proper paths to Project->Propoerties->C/C++ General->Paths and Symbols. If it does not help, you can configure Eclipse Code Analyser (which generates the 'errors') in Project->Properties->C/C++ General->Code Analysis. Under the error description you have problem with, try Customize Selected->Scope->Exclusion Patterns.

edited Nov 16 '11 at 08:47

answered Nov 16 '11 at 07:51

ondrisko

320
2
11

score 1 · Answer 9 · answered Dec 29 '12 at 06:49

1

I personally agree with compostus' answer.

It's good to solve the real problem that eclipse's code analyzer have.

But when I try this steps: define the symbol in Project -> Properties->C/C++ General -> Paths and Symbols

I don't find symbol tab or any place to add a symbol. what I want to do is putting macros like -DANDROID or #define ANDROID 1 to eclipse so that the code analyzer can find this definition.

I'm under Mac OSX mountain lion.

answered Dec 29 '12 at 06:49

fluke

660
8
16

2

`__BASE_FILE__` is predefined gcc macro. I don't want to redefine it :) – fasked Dec 29 '12 at 07:09
I'm having the same problem with multiple tabs not showing up and I'm runing Eclipse 4.2.1 and latest CDT on Ubuntu 12.04 – L7ColWinters Jan 24 '13 at 21:32

score 1 · Answer 10 · answered Jun 03 '14 at 17:31

adding as another answer, hopefully this will help someone.

I have a ~simple workspace (1 c++ shared-object (linux's version of a DLL, 3 c++ executables, and a pydev python project)

I checked out all the code to a new machine, and it builds fine but had numerous 'semantic errors' on std-c and std-C++ code and includes.. I went through all the discovery / indexer setting to no avail.

==> deleting the entire .metadata folder fixed this.

Since i had nothing non-trivial set up in the workspace (all in the project files / makefiles), eclipse happily created a fresh workspace, and i simply had to do a file->import-> existing projects

score 1 · Answer 11 · answered Oct 11 '14 at 14:45

If on Ubuntu, go to Window > Preferences > In Search box type "Indexer" > Select Indexer in left column. Under heading "Indexer Options" tick the following options (all but those involving the skipping of files):

Index files source files not included in project
Index unused Headers Index all header variants
Index source and header files openend in editor
Allow heuristic resolution of includes

Under heading "Indexing Strategy" tick both options which are:

Automatically update the index
Update index immediately after every file-save

Under heading "Build Configuration for the indexer" select the following option:

User active build configuration

I enabled all indexer options, except those for skipping files) in both Window > Preferences and project properties and it fixed the issue. — ivan_onys, Jan 23 '17 at 13:28

score 1 · Answer 12 · answered Feb 17 '16 at 10:34

1

try this:

Preferences --> c/c++ --> Indexer --> Index all header variants

check this option.

answered Feb 17 '16 at 10:34

user245225

11
1

score 1 · Answer 13 · answered Jul 09 '18 at 10:33

1

This is a file indexing issue.

Solution - Right click on the project, Index->Freshen all files.

(Applies to Eclipse CDT.Oxygen)

answered Jul 09 '18 at 10:33

George Eliozov

61
1
2

score 1 · Answer 14 · answered Jun 10 '20 at 18:42

In my case, I eventually discovered that the indexer was having problems because a colleague had “helpfully” duplicated a whole load of declarations in two header files that were only included together in a small subset of C files in the project. Removing the duplications (and making one header include the other) allowed the indexer to function correctly again.

It was particularly a problem with duplicated enumerations, for some reason. I do not know why this is so.

score 0 · Answer 15 · answered Mar 18 '14 at 14:29

I used #pragma once in my code. This configuration caused me to have the problem:

---fileA.h---

#pragma once
#define MYMACRO(X) func(X)

---fileB.h---

#include "fileA.h"

---fileB.cpp---

#include "fileB.h"

MYMACRO(5)  <---- warning here

I replaced #pragma once with #ifndef #define HEADER_FILE_H #endif, and that fixed the problem.

score 0 · Answer 16 · answered Aug 06 '15 at 17:16

Not sure if this works for the OPs issue, but I had semantic errors in eclipse Luna and was able to resolve them by following instructions in this thread: Eclipse shows unresolved inclusion but it compiles

The compiler finds the header, but Eclipse not.

You could help Eclipse and set the path to the header files under:

Project -> Properties -> C/C++ Build -> Settings -> Compiler -> Includes

In my situation, eclipse had determined one of my include directories, but did not determine that there were sub-include directories within it.

score 0 · Answer 17 · answered Dec 09 '15 at 22:26

I had a similar issue but my compile was fine but Eclipse showed errors on lines that used a #define from another include file. I fixed by checking "Index all header variants". I think the classis #ifndef FILENAME in include file was process multiple times in Indexer and so 2nd time the FILENAME was defined so all #defines in .h file were not "seen" by the preprocessor. Go to Window | Preferences | C/C++ | Indexer.

score 0 · Answer 18 · answered Feb 15 '16 at 15:03

I have the same problem. Compiler preprocesses ok, but static analyzer doesn't. In my source file:

#define PLATFORM_INC_FILES
#include <platform.h>

int coflags=O_BINARY; // Undefined symbol

In platform.h (an OS dependent header to help creating portable code):

#ifdef PLATFORM_INC_FILES
    #include <stdio.h>
    ...

It looks like static analyzer doesn't take the .c #define statements into account when preprocessing included headers. By defining it at the symbols dialog, errors dissapear, but that is a project scope symbol definition, resulting in every source to include every system header in my case.

Hope it gets fixed soon...

Using Eclipse Mars and MinGW on MSIS2.

score 0 · Answer 19 · answered Jul 12 '17 at 07:39

The problem occurs this way: I insert a new variable name into the code somewhere e.g. "newone" in this example:

int a;

foo()
{
  a=17;
  newone=23;
}

The file is saved (so the indexer is reindexing). Then I added the definition:

int a, newone;

foo1()
{
  newone=0;
}


foo()
{
  a=17;
  newone=23;
}

The indexer will still shows the error at the line " newone=23;" but not at the other lines of code containing "newone".

Solution: first define your variables, then use it.

M.

score -1 · Answer 20 · answered May 18 '13 at 02:09

In the past, I would define the ANDROID symbol in: Project -> Properties->C/C++ General -> Paths and Symbols -> #Symbols tab However, the latest version of Eclipse no longer has a # Symbols there, or anywhere else. It seems there is no longer any way of defining symbols in Eclipse. Eclipse has so many bugs and problems. I finally gave up and switched to using Gedit and the terminal to compile.

Eclipse CDT shows semantic errors, but compilation is ok

20 Answers20

Linked