MadExcept not executing leak test in all environments

delphi package - automated exception handling
Post Reply
Ross
Posts: 1
Joined: Thu May 30, 2019 6:05 pm

MadExcept not executing leak test in all environments

Post by Ross »

Update on Solution

Ok, if you found this topic because you are experiencing the same issue, ensure that you have put madExcept32.dll (or madExcept64.dll) on the system you hope to run a leak report on!

Problem

So this may be kind of a strange problem.

We have a licensed copy of MadExcept, and are using it to build a runtime .exe that includes MadExcept with exception catching and the leak test options enabled.

When the compiled .exe (compiled with CBuilder6) is ran in the development environment (a Windows 10 VM) then MadExcept works as expected: it catches an exception and performs a leak report. When this same .exe is copied to a production machine (Windows 7 embedded) then MadExcept _will_ catch exceptions, but _does not_ produce a leak report.

We've tested this .exe on several other machines, all Windows 10, and on some machines MadExcept works as expected, and on others... we get nothing for a leak report. There is nothing showing up in event viewer or any other dialog to inform of us of what might be causing this issue. We also ran the .exe in different compatibility modes to see if this changed anything, and it did not.

Any tips or suggestions would be well received in resolving this issue. Thanks!

Update
We compiled a small test application that will throw one exception when a button is clicked. We have confirmed that MadExcept will catch the exception on all machine, but again, will not provide a leak report on all machines. We compiled this test application with the freeware version of MadExcept, and the licensed version, and saw the same results for both.
iconic
Site Admin
Posts: 1065
Joined: Wed Jun 08, 2005 5:08 am

Re: MadExcept not executing leak test in all environments

Post by iconic »

ensure that you have put madExcept32.dll (or madExcept64.dll) on the system you hope to run a leak report on
So does this mean that the problem is solved now for you?

--Iconic
Post Reply