edbored
asked on
Delphi 7 integrated debugger blocked by anti-virus program
I have been using Delphi 7 in Windows 10 for quite awhile.
I use ESET Internet Security as my anti-virus/anti-malware protection.
A recent update in ESET has caused problems with D7 - when I run a program from the IDE, the program never starts - it appears as though ESET is blocking the "integrated debugger" from attaching to the process.
I can disable all protection and everything works.
I'm looking for alternate solutions - something I might be able to add as some type of exception rule in the anti-virus to allow the integrated debugger to work.
Is the integrated debugger actually "integrated" in delphi32.exe, or is it called by the IDE? That is, is there a DLL or exe that can be identified as exception to anti-virus program?
TIA.
EdB
I use ESET Internet Security as my anti-virus/anti-malware protection.
A recent update in ESET has caused problems with D7 - when I run a program from the IDE, the program never starts - it appears as though ESET is blocking the "integrated debugger" from attaching to the process.
I can disable all protection and everything works.
I'm looking for alternate solutions - something I might be able to add as some type of exception rule in the anti-virus to allow the integrated debugger to work.
Is the integrated debugger actually "integrated" in delphi32.exe, or is it called by the IDE? That is, is there a DLL or exe that can be identified as exception to anti-virus program?
TIA.
EdB
masnrock
Apparently, there have been a number of recent reports of that type of issue. Contact ESET support. That should help them start working on a fix.
Otherwise, all you could really do is set up and exclusion and hope that it works. Working with support is going to be much more with your while.
Try to debug another project, at least with totally different components.... Check if you're able to use debugger....
ASKER
Thanks to both - I'm waiting on ESET support, but I have a work-around.
A completely blank project (just "form1") loaded and ran perfectly.
Three other typical projects "hang up".
When I terminate the running process (from outside IDE), I get a message "Interface not supported".
That triggered a memory related to past issues with FastMM4.
Sure enough, if I add FastMM4, FastCode , and FastMove to the empty project, it hangs up whilst being invoked from IDE (in fact, it's only FastMM4 that causes grief).
Some fiddling with options, and it turns out that I can beat this if I do any of the following in the FastMM4Options file:
1) define DoNotInstallIfDLLMissing ( and remove the FastMM_FullDebugMode dll from output dir; or,
2) define LoadDebugDLLDynamically; or,
3) undefine FullDebugMode
I've tried setting exceptions onf FastMM_FullDebugMode and the Application itself - still causes problems.
Basically I can no longer use FastMM to report memory leaks from the IDE - but when I disable that, I still get the FastMM memory manager speed...
At this point, that's enough to keep working - unless you have other suggestions I could try?
Thanks again.
Cheers,
EdB
A completely blank project (just "form1") loaded and ran perfectly.
Three other typical projects "hang up".
When I terminate the running process (from outside IDE), I get a message "Interface not supported".
That triggered a memory related to past issues with FastMM4.
Sure enough, if I add FastMM4, FastCode , and FastMove to the empty project, it hangs up whilst being invoked from IDE (in fact, it's only FastMM4 that causes grief).
Some fiddling with options, and it turns out that I can beat this if I do any of the following in the FastMM4Options file:
1) define DoNotInstallIfDLLMissing ( and remove the FastMM_FullDebugMode dll from output dir; or,
2) define LoadDebugDLLDynamically; or,
3) undefine FullDebugMode
I've tried setting exceptions onf FastMM_FullDebugMode and the Application itself - still causes problems.
Basically I can no longer use FastMM to report memory leaks from the IDE - but when I disable that, I still get the FastMM memory manager speed...
At this point, that's enough to keep working - unless you have other suggestions I could try?
Thanks again.
Cheers,
EdB
It is nice that you detect reason.... My point was that some component or unit make your project be "nasty".
I use FastMM without a problem ... Try to use older/newer version of those units.
I use FastMM without a problem ... Try to use older/newer version of those units.
ASKER
In fact, I spoke too soon...
It looks like the only reason FastMM was causing issues was because FastMM was the only thing in the project trying to load a DLL.
I tried my "fix" on a real project, and it fails.
Or rather, it runs from IDE the first time, but if I close the program and run again, it fails to load.
This project loads many DLLs (odbc, midas.dll, database drivers, etc).
At this point the only workaround is to completely disable ESET protection...
It looks like the only reason FastMM was causing issues was because FastMM was the only thing in the project trying to load a DLL.
I tried my "fix" on a real project, and it fails.
Or rather, it runs from IDE the first time, but if I close the program and run again, it fails to load.
This project loads many DLLs (odbc, midas.dll, database drivers, etc).
At this point the only workaround is to completely disable ESET protection...
Here's a link to a post on ESET's Security Forum that I had found when I was checking to see how many people were having problems: https://forum.eset.com/top
So according to the last post there (from Marcos about an hour ago), ESET has found the issue and they're working on a fix for the problem.
So according to the last post there (from Marcos about an hour ago), ESET has found the issue and they're working on a fix for the problem.
ASKER
I just had an ESET client support person contact me with that same link!
Now my problem is how to close this question - who gets the "solution" credit - masnrock because you found that link for me?
Now my problem is how to close this question - who gets the "solution" credit - masnrock because you found that link for me?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks both - client support from ESET reached out to me- the fix is actually in their product, and will be released Real Soon Now (they roll-out in batches) - next week latest for general release. I can live with "remote debugging" for now.