Đang chuẩn bị liên kết để tải về tài liệu:
Memory Dump Analysis Anthology- P25
Đang chuẩn bị nút TẢI XUỐNG, xin hãy chờ
Tải xuống
Memory Dump Analysis Anthology- P25: This is a revised, edited, cross-referenced and thematically organized volume of selected DumpAnalysis.org blog posts about crash dump analysis and debugging written in 2006 - 2007 for software engineers developing and maintaining products on Windows platforms, technical support and escalation engineers dealing with complex software issues and general Windows users. | 692 PART 13 Miscellaneous THE ELEMENTS OF CRASH DUMP ANALYSIS STYLE After looking at multitude of crash dump analysis reports from different companies and engineers I would like to highlight several rules that make them good Format your debugger output in fixed size font Courier New or Lucida Console . This is very important for readability. Bold and highlight using different colors important addresses or data. Keep the same color for the same address or data consistently. Use red color for bug manifestation points. If we refer to a dump files we should put a link to it. What is considered bad crash dump analysis style These are Variable size font you copy your debugger output to Outlook e-mail as is and it is using the default font there. Highlight the whole data set for example stack trace in red. Too much irrelevant information. Crash Dump Analysis in Visual Studio 693 CRASH DUMP ANALYSIS IN VISUAL STUDIO If we open a user crash dump as a solution project not a as file then we can do crash dump analysis by using Visual Studio debug windows for example powerful Watch window. As we can see from the picture below I loaded a crash dump from my test application saved by NTSD and it shows assembly code and source code nicely interleaved. If we need to specify additional symbol paths or symbol server settings we can do it in Tools Options Debugging Symbols dialog. 694 PART 13 Miscellaneous This might be good for engineers used to do live debugging in Visual Studio and having no experience in using WinDbg if they need to look at application crash dumps from .