Summary


This chapter helped demystify the process of what you do to pinpoint the location of a crash when the only information you have is the crash address. The first technique for finding out the source file and line number of a particular crash is to refer to a MAP file. MAP files are the only textual representation of your symbols, and you should create them routinely for every release build of your application. The second technique for converting a crash address to a source file, function name, and line number is to use CrashFinder. The CrashFinder utility takes all the work out of making this conversion and allows others on your team to report as much information as possible when the application crashes on them. Although CrashFinder is easier to use than MAP files, you still need to get into the habit of creating MAP files because symbol file formats change—and when they do, only your MAP files will save your soul when the ghost of applications past comes knocking at your door.




Debugging Applications for Microsoft. NET and Microsoft Windows
Debugging Applications for MicrosoftВ® .NET and Microsoft WindowsВ® (Pro-Developer)
ISBN: 0735615365
EAN: 2147483647
Year: 2003
Pages: 177
Authors: John Robbins

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net