Will a DLL with a shared data segment cause it to be flagged as suspicious? We added this function to a DLL and it is now being flagged.
Upload and test suspicious files at one of these places… post link to scan result(s) here
www.virustotal.com / www.metascan-online.com / www.jotti.org
If you think detection is wrong, you can use one of these options and report it
You can upload files and report issues to avast here : http://www.avast.com/contact-form.php (select subject according to Your case)
You can use mail
send to virus@avast.com in a password protected zip file
mail subject: False Positive / undetected sample (select subject according to your case)
zip password: infected
or you can send files from avast chest
how to use the chest. http://www.avast.com/faq.php?article=AVKB21
We can do that, but it appears it is just the shared segment that is the problem. I commented out these three lines:
//#pragma data_seg (“.MYSHARED”) // Begin the shared data segment.
//wchar_t gURLString[URL_STORED_SIZE] = {0};
//#pragma data_seg() // NOTE: This must be in the linker commands: /SECTION:.MYSHARED,RWS
and replaced it with
wchar_t gURLString[URL_STORED_SIZE] = {0};
and it no longer flags as suspicious. So I can submit the compiled DLL, but if the mere existence of a shared segment results in a flag, would we need to submit each and every new version of the DLL that we release?