Page 1 of 1
Purebasic with debugger Mcaffee blocks
Posted: Sat Sep 01, 2018 11:43 am
by HPW
Hello,
When I test with any example with compile/start with enabled Debugger, my Mcaffee real-time protection blocks the exe.
First comes a message that purebasic cannot use the internal Debugger and then Mcaffee Pops up about isolating purebasic_compilation0.exe with a GenericRXCL...... Virus.
What can I do?
Regards
Re: Purebasic with debugger Mcaffee blocks
Posted: Sat Sep 01, 2018 12:02 pm
by Dude
You need to add PureBasic.exe and its related files to McAfee's white list.
Re: Purebasic with debugger Mcaffee blocks
Posted: Sat Sep 01, 2018 12:21 pm
by HPW
Hello,
I have purebasic.exe in my whitelist.
What do you mean by 'related files'?
I can not configure Mcaffee to exculde a Folder from realtime-protection.
And it complains about the temp-exe.
Regards
Re: Purebasic with debugger Mcaffee blocks
Posted: Sat Sep 01, 2018 12:24 pm
by Dude
Related files are "purebasic_compilation0.exe", etc. Why can't you configure McAfee to ignore PureBasic's folder? That should be a basic feature of any good AV software. Or is McAfee that bad?
Re: Purebasic with debugger Mcaffee blocks
Posted: Sat Sep 01, 2018 6:39 pm
by HPW
Hello,
>>purebasic_compilation0.exe
Ok, but it is not practical to enter each new testfile in every related path into the Whitelist which can be only done from admin account.
And you can not set Folders to exclude from the real time protection. You can only do it for Virus scans. So it is that bad.
Regards
Re: Purebasic with debugger Mcaffee blocks
Posted: Sat Sep 01, 2018 7:43 pm
by Little John
HPW wrote:Ok, but it is not practical to enter each new testfile in every related path into the Whitelist
If the marked option is not checked (like on the above picture), then the temporary executables (PureBasic_Compilation0.exe, PureBasic_Compilation1.exe etc.) are all created in the
%temp% directory. Putting these files on the whitelist shouldn't be too much of a problem.
Re: Purebasic with debugger Mcaffee blocks
Posted: Sun Sep 02, 2018 2:24 am
by Dude
HPW wrote:it is not practical to enter each new testfile in every related path into the Whitelist
You can always wildcard them in your AV with an asterisk at the end, to cover all possibilities:
Code: Select all
C:\Users\[UserName]\AppData\Local\Temp\PureBasic_Compilation*
I've done this with Avast, and I
never get a warning when compiling my apps.
If McAfee is any good, it should have the functionality to wildcard files as well.
Re: Purebasic with debugger Mcaffee blocks
Posted: Sun Sep 02, 2018 1:47 pm
by Bitblazer
Dude wrote:I've done this with Avast, and I never get a warning when compiling my apps.
Kaspersky is also fully compatible with Purebasic development and always ranked among the top products in
antivirus tests.
Re: Purebasic with debugger Mcaffee blocks
Posted: Mon Sep 03, 2018 12:49 pm
by blueb
... Kaspersky is also fully compatible with Purebasic development and always ranked among the top products in antivirus tests.
I've used Kaspersky for perhaps 5 years and have found it very reliable and trouble free.
