search

saaadhu / naggy

A live compiler diagnostics extension for Atmel Studio
18 stars 4 forks source link

Assertion failed! #60

Open Mehradzie opened 6 years ago

Mehradzie commented 6 years ago

Hi there,

Recently got this strange error popping-up when I removed a random line of code from my program on Atmel Studio 7 (Version 7.0.1931) that I tracked it back to Naggy 0.4.0 from the hints on the error message. Taking Abort and Retry options closes down Atmel Studio and Ignore puts the error message to sleep for 5s before it pops up again.

As you could see on the attached image, the body of the message indicates:

Microsoft Visual C++ Runtime Library Assertion failed! Program: .... STUDIO\7.0\EXTENSIONS\fwao2ivd.541\Naggy.Clang.dll

I have disabled Naggy and the issue went away, but I'd be keen to enable it back up again as I use it extensively.

Not that it matters but the line of code I was removing or even commenting out was the 3rd line of the code below:

#include <asf.h>
#include "my_tasks.h
#include "conf_demo.h"             <---------------

// \name Task configuration
#define UART_TASK_PRIORITY          (tskIDLE_PRIORITY + 3

atmelstudio_naggy

kutukvpavel commented 6 years ago

I can confirm the presence of the bug. Has something to do with includes, appeared after I added a couple of them (by typing, it seems to ignore the ones already present in the file). It seems it disappeared after removing the extension, adding necessary includes and installing the extension again. Also when a path contains unicode the extension fails to find (underlines red and displays file not found error) included file (though it is present in intellisense list and compiles fine). Probably unicode had something to do with the issue, but I am unable to reproduce it after modifying the source files reinstalling the extension, so I can't tell for sure. Pretty frustrating.

hobala commented 8 months ago

We, too have this problem with some of our projects but - so far - could not find out what would be the reason for this behavior. Any ideas, how to debug this?