LMAETC10

LMAETC10 - 95 CHAPTER 1 Debugging in the Windows Operating...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: 95 CHAPTER 1 Debugging in the Windows Operating System \z "TOPICW.DOC-1001" \z "TOPICW.DOC-1002" \z "TOPICW.DOC-1003" The Microsoft CodeView for the Windows operating system debugger (CVW) is a powerful tool for analyzing the behavior of Microsoft Windows-based programs. With CVW, you can test the execution of your application and examine your application’s data. You can isolate problems quickly because you can display any combination of variables — global or local — while you halt or trace your application’s execution. Comparing CVW with CV The CVW windows, menus, and commands are used in the same way as for CV. See Chapter 9, “The CodeView Environment,” for details on the format of CodeView windows and how to use the windows and menus. Like the MS-DOS CodeView, CVW allows you to display and modify any program variable, section of addressable memory, or processor register. However, CodeView for Windows differs from CV in the following ways: u Because the Windows operating system has a special use for the ALT+/ key combination used by CV to repeat a search, CVW uses CTRL+R . u CVW tracks your application’s segments and data as the Windows operating system moves them in memory. Thus, when you refer to an object by name, CVW always supplies the correct address. \z "TOPICW.DOC-1004" \z "TOPICW.DOC-1005" \z "TOPICW.DOC-1006" \z "TOPICW.DOC-1007" \z "TOPICW.DOC- 1008" \z "TOPICW.DOC-1009" \z "TOPICW.DOC-1010" \z "TOPICW.DOC-1011" \z "TOPICW.DOC-1012" \z "TOPICW.DOC- 1013" \z "TOPICW.DOC-1014" \z "TOPICW.DOC-1015" \z "TOPICW.DOC-1016" \z "TOPICW.DOC-1017" \z "TOPICW.DOC- 1018" CVW also provides six additional Command-window commands for Windows- based program debugging, which are summarized in the following list: Special Topics Filename: b702dd0a808bdb50c2ac2a7d35edcfa258c39bce.DOC Project: Template: Author: Last Saved By: Revision #: 0 Page: 95 of 33 Printed: 10/12/92 16:07 A10/P10 Environment and Tools Windows Display Global Heap ( WDG ) Displays memory objects in the global heap. Windows Display Local Heap ( WDL ) Displays memory objects in the local heap. Windows Dereference Local Handle ( WLH ) Dereferences a local heap handle to a pointer. Windows Dereference Global Handle ( WGH ) Dereferences a global heap handle to a pointer. Windows Display Modules ( WDM ) Displays a list of the application and DLL modules currently loaded in the Windows operating system. Windows Kill Application ( WKA ) Terminates the task that is currently executing by simulating a fatal error. For details on using these commands, see “CVW Commands” on page 357. The following CV features are not available in CVW. u The Print command from the File menu. u The DOS Shell command from the File menu and the corresponding Shell ( ! ) Command-window command....
View Full Document

This note was uploaded on 01/24/2012 for the course EE 3751 taught by Professor Desouza during the Spring '04 term at LSU.

Page1 / 33

LMAETC10 - 95 CHAPTER 1 Debugging in the Windows Operating...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online