Reputation: 1
We have been trying to solve this problem which is causing our program to crash. However, we haven't been able to reproduce the crash in house.
The call stack that is coming from the client's machine is on the link here:
Click to enlarge:
It doesn't seem to have any reference to any of the file in our project, so we're a bit lost as to where to look for a solution.
Could this be an environmental issue? The clients' that are getting this problem is using Windows 7 SP1 and Windows Server 2003. Sometimes, just prior to crash, the customer has been reporting that they have been getting 'A call to an OS function failed' error messages. Can this be related? Based on the call stack, can anyone make sense of what it is trying to do?
[Update] The call stack came from EurekaLog. Also I attach below the call stack from the 'A call to an OS function failed' error, that the customer is experiencing as well. This seems to be related to the AV error that the customer is getting but we are not sure. http://postimage.org/image/jku5dlnuf/
Upvotes: 0
Views: 994
Reputation: 125757
Based on the portion of the stack trace in your image, it's impossible to tell. The stack trace is mostly showing Windows API internal functions from the kernel DLLs.
Exceptions with an address of all zeros is a nil pointer (an object being used before it's created), but there's no way to tell where it's happening from that stack trace.
You should look at adding an exception handling product like MadExcept or EurekaLog to your application, which would give you a usable stack trace and more error information. Both are relatively inexpensive, especially when compared to the time spent trying to track down this type of error without them. (My own experience is with MadExcept, but I'm not affiliated with either of them.)
Upvotes: 1