This is not a compiler bug or something that can be solved by them. The fact that the AV would no longer flag your program when you turn off the debug information might suggest that the trigger is indeed something that would get stripped off in a non-debug build (e.g. This "something" might be a string you've used, a particular sequence of machine instructions, or even a function name. If nothing else on your hard drive is being flagged as malware by your antivirus, then this "detection" is most probably because something in your program is triggering a heuristic detection routine inside the AV.
BUT unfortunately, I have to use BitDefender, and some of those computer that my program will be running at are using it as well.(my program is just a debugging tool for internal use only) I know this is kind of like a false positive virus since only some "unnamed" antivirus software report this. Hard drive scanned clear by multiple well-known antivirus program.Įxecutable is clear if I turn that to "No" without doing any other changes. I don't see any possible way this make my executable become virus. Then I look at what exactly it does, it says "This option enables creation of debugging information ofr the. When it is "No", not virus, when it is Yes, virus. So I then compare the setting difference, turns out Linker-Debugging-Generate Debug Info is the problem. I have a few configurations, this happens to only one of them.
#Bitdefender white label software program update
Here is the scan result from Antivirus Result Update I am working on a MFC project, and recently my antivirus software BitDefender sees my executable as virus " Gen:Variant.Razy.47148" This is one of the weirdest things ever happen to me in my programmer career.
0 kommentar(er)
