Our test process occasionally crashed with an access violation exception. We consider these to be Priority 0 bugs, so we had one of the most experience developers in the office sit on this problem.
Access violation errors are nasty, because they give you very little information about what is going on, and there is typically no real way to recover from them. We have a process to deal with them, though. We know how to set up things so we’ll get a memory dump on error, so the very first thing that we work toward is to reproduce this error.
from DZone.com Feed http://bit.ly/2GRtr47
No comments:
Post a Comment