I have a user that started experiencing access violations related to his shell32.dll file when using my software. This started to occur after upgrading to the latest version of our software, which is the first version we released that had been compiled in D2009.
No one else is reporting these AV problems, and I have been unable to replicate them myself. So it seems that it has something to do with his particular installation of Windows. I use EurekaLog, so I can tell that some of these AVs have to do with the creation or display of various forms in the application. Often, the following reference is given as the last thing the call stack:
shell32.dll > ILIsEqual
Does anyone have any ideas on how I can get this user going again? Or how I can get more clues as to what's actually the problem? In the past, I've found these errors that only occur on one user's machine to be very difficult to track down….
Best Answer
I agree, it is hard to replicate such errors. This is why quality logging is so important. I would use a following approach with such a problem.
If you have time you can also talk with the user. This way sometimes they tell you important new info that can help you.
I had two nasty bugs to find in the last week or so. I just started to methodically move towards the goal. And when I picked up the scent of the error it was just a matter of time finding it. I found out that if you are methodical, sooner or later you will find the cause.