Classic Software recommended: AppVerifier (Application Verifier)

"Bugs" in the most headache is the kind of: wild pointers, invalid handles, access violations, and the Windows kernel to deal with more of those, they find difficult, debugging difficult, difficult to locate. But AppVerifier is the tool to solve these problems, in fact, Microsoft-led large Windows software developers are using this software as a supplementary test. I recommend it here, in addition to its good grasp of these relatively kernel, the underlying bug, is Microsoft produced, free to use and very simple is a number of other factors. AppVerifier's objective introduction AppVerifier can be downloaded for free, especially for detecting and helping debug memory corruption, dangerous security vulnerabilities, and limited User account privilege issues. AppVerifier helps you create a reliable and secure application by monitoring your application with Microsoft? Windows? The interaction of the operating system and configures the objects, registry, file system, and Win32 APIs (including heaps, handles, and locks) that the application uses. AppVerifier also includes checks to predict how the application will perform in a non-administrator environment. This is the original version of Microsoft MSDN. MSDN recommends using it in "C + + security best practices" to verify software security. MSDN even advocates the use of this software throughout the development life cycle: "When used throughout the software development lifecycle, AppVerifier can save on development costs because it facilitates early identification of problems, and early bug fixes are easier and less costly." "AppVerifier can identify the problem AppVerifier help to determine: (Copy on MSDN)?" The application correctly uses the API moment:? Insecure TerminateThread API.? Correct use of thread local storage (the thread locally storage,tls) API.? Use virtual space operations correctly (for example, VirtualAlloc and MapViewOfFile). Whether the application uses structured exception handling to hide access violations.? Does the application attempt to use an invalid handle.? Is there memory corruption in the heap or is there a memory problem? Is the application running out of memory in the case of insufficient resources? is the critical section used correctly? Does an application running in an administrator environment work well in a low-privileged environment? Is there a potential problem when the application runs as a restricted user? In the context of a thread, uninitialized variables will be present in future function calls. The use of AppVerifier is described below with its own application (very simple). 1. Download APPverifier on the Microsoft website and install the software http://www.microsoft.com/downloads/details.aspx? Familyid=bd02c19c-1250-433c-8c1b-2619bd93b3a2&displaylang=en2. Run AppVerifier to add applications that need to be validated in AppVerifier, and for developers to directly select the debug version of the executable file that is output in the project, multiple files can be added, or dynamic library DLLs can be added. 3. Configure the items that need to be validated AppVerifier can roughly verify the pitfalls of 18 aspects (version 3.3) of exceptions, handles, stacks, memory, uninitialized parameters, select the items that need to be tested, and save the settings. 4. Debugging programs in the IDE these are the same as before, but during the debugging process AppVerifier will report to you the problems it detects, in an unusual way, or output the information to the output box, in general, the program stops at the place where the problem occurs. 5. Cancel validation cancels the program to be validated in AppVerifier, otherwise the validation code is hung in the program. Well, first good at the software to try it, before there are no errors, now, more out of a lot of anomalies, hurriedly see .... Another software with it is the same series: Driver Verifier, specifically to test drive security. References: Interested colleagues Google "application Verifier" to see the introduction. Colleagues who want to learn read MSDN: Using Application Verifier in the software development lifecycle http://www.microsoft.com/china/MSDN/library/enterprisedevelopment/ Softwaredev/wddnclinicscripting.mspx?mfr=true using Application Verifier to troubleshoot program issues in Windows XP http://support.microsoft.com/ DEFAULT.ASPX/KB/286568/ZH-CN "C + + security Best Practices" HTTP://MSDN2.MICROSOFT.COM/ZH-CN/LIBRARY/K3A3HZW7 (vs.80). aspx

Classic Software recommended: AppVerifier (Application Verifier)