I've started getting Access violation at address 00007D42. Read of address 00007D42 or other various addresses such as 0000028, 0000000, 00006574
or External exception C000001D.
Seems like when I type something it does this, hit ok then it's fine again till after I type something again. It still compiles everything but hard to write code if you have to hit enter every time you type something. Has this happened to anyone yet? I've also just reinstalled and same thing, I've put nothing new on this computer at all since this was originally installed.
Access violation
Hi Picer,
You are not alone!
I've been having this for some time but as I'm often installing/uninstalling its difficult too know where the problem is. I finish up relaunching the application which works for a while untill I change something simple such as a variable!
Could also be something to do with A/V software or heaven forbid - a Microsoft update!!!
You are not alone!
I've been having this for some time but as I'm often installing/uninstalling its difficult too know where the problem is. I finish up relaunching the application which works for a while untill I change something simple such as a variable!
Could also be something to do with A/V software or heaven forbid - a Microsoft update!!!
Be kind and like your words - you never know, you may have to eat them one day!
Hello,
just my 2 cents.
I am developing a quite long program (about 4.000 lines of code) for a dsPIC + display, and I also suffered some things like those you pointed.
Normally the access violation requires only a restart of mikroC, then if the code is ok it is compiled without other problems.
Other strangeness is related to float variables. Many times the cursor goes to the first global float declaration of a variable with a compile error or access violation, then with restart all goes fine.
Some days ago I added to a well compiling/functioning code a block of code containing some float (local at the beginning of the function) declarations of variables (some temperature check of the devices, e.g. temperature = Analog_read(...); if(temperature<-8.0f) do something), and I wasn't able to compile this code, because every time I got access violation, until I set up casting with signed int and all went fine. So I guess there is also something related to float variables.
Best regards,
picdog
just my 2 cents.
I am developing a quite long program (about 4.000 lines of code) for a dsPIC + display, and I also suffered some things like those you pointed.
Normally the access violation requires only a restart of mikroC, then if the code is ok it is compiled without other problems.
Other strangeness is related to float variables. Many times the cursor goes to the first global float declaration of a variable with a compile error or access violation, then with restart all goes fine.
Some days ago I added to a well compiling/functioning code a block of code containing some float (local at the beginning of the function) declarations of variables (some temperature check of the devices, e.g. temperature = Analog_read(...); if(temperature<-8.0f) do something), and I wasn't able to compile this code, because every time I got access violation, until I set up casting with signed int and all went fine. So I guess there is also something related to float variables.
Best regards,
picdog
... a proud user of MikroElektronica EasyPic3, EasyPic4, BigPic4, MikroC for PIC, EasydsPIC2, dsPIC-Pro2, LV24-33 and MikroC for dsPIC :)
Re: Access violation
Another thing that might cause an access violation is silly syntax errors like not including a pair of () between the name of an ISR and the org directive... 
easy, compiler!...
For instance, writing (as I did...) void CAN_Int org 0x4A and not void CAN_Int() org 0x4A, drove me nuts for a while...
until illumination! ...D'OH!
Happens to the best... well, a bit like me a-hum
easy, compiler!...For instance, writing (as I did...) void CAN_Int org 0x4A and not void CAN_Int() org 0x4A, drove me nuts for a while...
until illumination! ...D'OH!Happens to the best... well, a bit like me a-hum
Re: Access violation
Notice you haven't adopted the new way then.....
void CAN_int() iv IVT_ADDR_C1INTERRUPT {
// Your interrupt code here.......
}
I know.... Change is painful....
Best regards
cjogo
void CAN_int() iv IVT_ADDR_C1INTERRUPT {
// Your interrupt code here.......
}
I know.... Change is painful....
Best regards
cjogo
