He then suggested using a spy app to monitor the messages his windows are getting, and in doing that I noticed the madExcept window and wondered if there might be something happening? Of course the problem only happens randomly, about every three days or so, and isn't leaving any traces other than the DrWatson traces. It is also definitely not happening in my DLL, though it is still loaded at the time.(It seems to be sending it to a WndProc address at 0140a874, in the 1st &
3rd cases, nothing was there, in the second case, by chance, the Sophos
OSDP.DLL had loaded itself into that memory area)
No one else has ever reported this problem to us!
I can't think how you could cause that problem, but I can't see how it
could happen because of my app for you, but not for anyone else.
Either there's something which is trying to hook one of my app windows
and is getting it wrong (or unloading itself prematurely), or something
else is creating a hidden window with the wrong WndProc address being
registered, or something bizarre is happening.
If you have any thoughts on this, whether it might be madExcept, and what I might do to modify the behaviour (or things I probably forgot to enable as I usually just use madExcept in apps), I'd love to hear your thoughts.
Matthew