AS6.1 reports errors where there are none

Go To Last Post
6 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi

Alright, how do I explain this best?

It seems that AS6.1 sometimes gets a little bit confused (or is it actually Visual Assist). I've attached two pictures to show what I mean:

The error window shows me two errors (sometimes I also get different errors here and sometimes some warnings such as "Input not relaxable" are shown). The Output Window on the other hand shows that the build was successful AND I double-checked: a new hex/elf file is being generated.

I can do a full rebuild and it will still show these errors. The output window again says: Everything fine, 1 succeeded.

It seems like AS6.1 doesn't forget about previous errors.

Once I close AS6.1 and reopen the very same project, the errors are gone.

Any idea how I can tell AS6.1 to
* either do not show the error list anymore since it's of no use anyway
* or tell atmel studio to not show such stupid information

I have a feeling that this comes from Visual Assist or similar since uint8_t is always defined, I just had it in a header file which doesn't explicitly include . So it's not even a one-time real error (no complaints from GCC).

Attachment(s): 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Ok, some more info: Just discovered that these errors also disappear if I close all source code windows.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Are you using Naggy? I see it doing this sometimes - I get "wrong errors" in the Error window but the build is successful.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Damn you Spam Filter, I thought nobody would respond :(

Yes, in fact i'm using Naggy - I'll have to check if the problem occurs without Naggy as well.

Thanks for your response.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Yes, it's Naggy if the errors go off if the corresponding source windows are closed. Were those errors from header files? If not, do you mind sharing the errors so I can add it to the blacklist (if it makes sense)?

Regards

Senthil

 

blog | website

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

saaadhu: What do mean by "sharing the errors"? The errors themselves are ok (I guess they were really somewhere in the code). After fixing the code, Atmel Studio could build the ELF/HEX successfully, but still showed them. So the error itself is ok, it just didn't get updated after/before compilation.