I've seen that happen far too often in C++ code emitted from Visual Studio 2005 and 2008. It's a hoot.
This is so comical I had to laugh.
I sat down at my computer this morning to bang out a little file conversion Console Application in Visual Studio. I need to convert some files from a file format called ".CAP" to another format called ".SCP", so I named my console app "cap2scp". To get started, I typed in a simple main function and compiled it.
To my surprise, AVG popped up and said that the file "cap2scp.exe" was infected with something called "HackTool.ONO" - AVG actually prevented the linker from writing the just-compiled executable to disk.
Here is the complete source code for this "virus:"
int main (int argc, char* argv)
Apparently I made the mistake of choosing a name for my program that is the same as some nebulous "Hack Tool," and AVG's in-depth analysis doesn't extend past the blacklisted filename. Adding an exception for the file did no good, probably since AVG prevented the file from being written to disk in the first place; when I added the exception and recompiled my program, AVG popped up again with the same warning. I had to disable AVG in order to continue working on my program.
Anyway, I'm sure some of you out there will get a chuckle out of this.