We have a DLL that is used by an Outlook add-in (also ours). ESET Nod32 A/V Outlook add-in is causing this DLL to fail with their latest update.
ESET has said that our DLL is writing to memory in their scope, “according to the analysis from our developer, this crash is explicit bug in IDMx.dll (this plugin try to (wrongly) modify memory which contains our code/function).”
I find that hard to believe, the DLL (with slight modifications over the years) has been working fine for decades. Is there an easy way I can track all memory locations our DLL writes to, especially any memory outside our scope?