So many will be familiar with the long running sage of problems with CCC.exe (AMD / ATI Catalyst Control Center), some may have experienced problems first hand.
AMD Radeon Software History - Wikipedia
File mapping on compile process - ClarionHub
9.1 beta 1 - 10638 FEATURE:: Before building if the process CCC.EXE is found running the IDE will try to stop it, if is successful it will add a message in the Error List (Message) This was added to stop the error on building related to the Catalyst Control Center Utility (aka CCC.EXE)
Its possible that your dev machine may have been hacked!
I’ll explain why, so in most devices there is at least one CPU, however sometimes there is more than one like Graphics Card GPU’s, and because CPU’s dont know what instructions they should be calling, if you can get access to one of these extra CPU’s you have the ability to interact with the main device. Only the design of the circuit and international standards for Buses along with software measures could restrict some or all of its activities.
Looking back, examples in computer security exist.
2013 - You Can Type, but You Can’t Hide: A Stealthy GPU-based Keylogger)
More recently
2021 - Cybercriminal sells tool to hide malware in AMD, NVIDIA GPUs (bleepingcomputer.com)
Examples of other devices (mobile phone) with secondary processors (simcard have processors) interacting with the main device.
What is AT&T doing at 1111340002? (scribe.rip)
So if you have experienced this problem with CCC.exe in Clarion, you may actually be best advised to take out your graphics card and rely on your main cpu graphics capabilities, if it has any.
If you cant do that, look at other measures even a decent firewall that blocks outgoing access by default!
So just killing the CCC process may not be enough because they might have got embedded elsewhere in a system and there is a window of opportunity between the CLW generation and the compilation into a DLL or EXE.
In fact most dev’s probably dont even check if their CLW’s match whats in their app files!
Certainly not checking all code before compilation is a complaint that can be levelled at all developers, not just Clarion devs.
So what would be the best way to reduce this window of opportunity to inject malware source into source code just before its compiled?
Any suggestions?