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
Purebasic with debugger Mcaffee blocks
Purebasic with debugger Mcaffee blocks
Hans-Peter
Re: Purebasic with debugger Mcaffee blocks
You need to add PureBasic.exe and its related files to McAfee's white list.
Re: Purebasic with debugger Mcaffee blocks
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
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
Hans-Peter
Re: Purebasic with debugger Mcaffee blocks
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
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
>>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
Hans-Peter
-
- Addict
- Posts: 4777
- Joined: Thu Jun 07, 2007 3:25 pm
- Location: Berlin, Germany
Re: Purebasic with debugger Mcaffee blocks
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
You can always wildcard them in your AV with an asterisk at the end, to cover all possibilities:HPW wrote:it is not practical to enter each new testfile in every related path into the Whitelist
Code: Select all
C:\Users\[UserName]\AppData\Local\Temp\PureBasic_Compilation*
If McAfee is any good, it should have the functionality to wildcard files as well.
Re: Purebasic with debugger Mcaffee blocks
Kaspersky is also fully compatible with Purebasic development and always ranked among the top products in antivirus tests.Dude wrote:I've done this with Avast, and I never get a warning when compiling my apps.
Re: Purebasic with debugger Mcaffee blocks
I've used Kaspersky for perhaps 5 years and have found it very reliable and trouble free.... Kaspersky is also fully compatible with Purebasic development and always ranked among the top products in antivirus tests.

- It was too lonely at the top.
System : PB 6.21(x64) and Win 11 Pro (x64)
Hardware: AMD Ryzen 9 5900X w/64 gigs Ram, AMD RX 6950 XT Graphics w/16gigs Mem
System : PB 6.21(x64) and Win 11 Pro (x64)
Hardware: AMD Ryzen 9 5900X w/64 gigs Ram, AMD RX 6950 XT Graphics w/16gigs Mem