![]() ![]() These new techniques led me toward the holy grail of developers: being able to see a stack trace of each function that led up to the crash. Dawson's paper discusses several techniques that I had never encountered before, including how to capture the instruction pointer (ip) of a crash, and how to plug the ip into VC++ and go directly to the source line of the crash. This was the state I was in when I read Bruce Dawson's paper on Release Mode Debugging. Writing to the event log or other log file may be helpful, but can only point in a direction, not give a precise location. There is often no direct access to the customer's system, because of distance. ![]() But on the customer's system, there are random crashes. On the developer's workstation, the program works fine. One of the biggest challenges for a developer is to debug a program that has been put into production or shipped to a customer. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |