Not sure if this is the section of the forum to post to with my question, so if it is in the wrong place, please excuse me.
My set up is Eclipse 3.7 Indigo with the AVR Eclipse Plugin 2.3.4 and WinAVR20100110 on a Windows 7 PC.
The issue I am having is sometimes (and I really mean only sometimes) Eclipse will show a little bug off to the side of some code I have written. When hovering the mouse over the bug I get the a pop up telling me that I have an unresolved symbol. The symbols that it cannot resolve are the AVR bit and register defines.
Here is what is not making sense, I will start a new project, configure for a mega48, and in my main.c file I will include avr/io.h, which includes iom48.h and iomx8.h which has the register defines. When I set a bit in a register (doesn't matter which bit or which register) I get the little bug on the side, which shows the symbols unresolved. I made sure all my tool chain settings were correct (Eclipse can find the include files no problem). I checked the Codan (Eclipse Code Analysis tool) settings, but didn't find anything that would explain the issue. So I built the code and it compiled and linked just fine. Downloaded to my AVR, and the program ran as expected. So I started another project the exact same way, and this time I did NOT get the little bug on the side - all symbols were resolved. Downloaded the code, and again everything ran fine.
So for some reason I am getting a false positive, and don't even know what part of Eclipse is causing it. I checked the Eclipse and CDT forums, but did not find anything remotely close to this issue. I did some searching on this forum, but haven't seen this issue posted yet. I did see the post about making sure in the .project file I need to have the AVR Eclipse plugin showing in the
Well like I said this only happens every once in a while, but I would like to resolve it because I don't want to miss a real unresolved symbol. Ignoring the issue doesn't mean everything is working correctly.
Sorry it is long winded, but I want anyone looking at this to understand the issue. Has anyone run into this before? I don't remember if I had seen this in Eclipse 3.6 (Helios), so I am not sure if this just started with Indigo.
Thanks for any help,