Problem with codeblocks IDE: Resolved

[daniel49]

Couple of years ago spent some time learning some basics of C until eventually it got thrown on the backburner and I quit trying to learn.
Am trying to rekindle desire to learn and have opted to just go with c++ since a lot of the basics are very similar.
I downloaded codeblocks-8.02mingw and installed it on a virtual xp machine on virtualbox in Mint Linux.

Installation went fine and used the compiler for about a week with no problems.
Today I fire it up and get the error message:



Runtime error!
Program C:\Program files\codeblocks\codeblocks.exe
This application has requested the Runtime to terminate it in an unusual way.
Please contact the applications support team for more information.



In short it won't run.
Reinstalled it= same result
uninstalled it completely and reinstalled it- same result.
did a restore back to when the compiler was still working- same result.
anybody got an idea whats going on?
thx in advance.



Edit:tried reinstalling codeblocks, microsoft runtime libraries, tried repair on xp, tried restore.
Finally just started over and created new virtual machine, reinstalled codeblocks and works fine.
not sure what got borked or how

 

[Cogman]

Codeblocks is not a compiler, it is an IDE. Mingw (a derivation of gcc) is the compiler which code blocks uses. (thought it can use microsofts, bordlands, ect).

I've never seen this bug before. Can you post some more information regarding the crash?

 

[daniel49]

Codeblocks is not a compiler, it is an IDE. Mingw (a derivation of gcc) is the compiler which code blocks uses. (thought it can use microsofts, bordlands, ect).


My Bad.



I've never seen this bug before. Can you post some more information regarding the crash?

Not really that was the error message in its entirety.
event viewer shows nothing.
if something was corrupted you would have thought a restore ( or a reinstall) to a happier time, would have straightened it out?

PS Am not sure but yesterday was running late for work and may have hurriedly closed the virtual
machine improperly? just a guess?