![]() Clicking an API failure error in The Events Browser opens the Parameters and Failures page and selects the indicated error as the active event in the Event view. ![]() The second column specifies the type of failure, memory, or resource associated with the error. The first categorized the event as an API or other failure, a memory error, or a resource error. The events in the Event Browser are filtered by call hierarchy-only one instance of each error from each call location is shown in the Event Browser. Each item in this view indicates a separate event (error) in the program. On the left hand side of the window is the Event Browser. ![]() The page includes three resizable views: the global Event Browser, the Event view, and the Stack Trace view. Clicking an API failure listed in the Event Browser view opens this page. This page is only active if the API Function Failures, API Function Parameters, or both options are checked. The stress testing feature, which is new in this version of the tool, can show you how your project will behave in resource poor environments. Finally, you can use Quality Suite CodeWatch to stress test your project. Quality Suite CodeWatch also includes features such as API compliance checking that can help ensure that your program will run properly on the target operating system for deployment. It does this by carefully monitoring your running program to find memory and resource leaks as well as errors in calls to Windows API routines. The primary function of CodeWatch is to help you find bugs in your project.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |