09.02.2014 Views

Windows sysinternals

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 7 Process and Diagnostic Utilities 239<br />

The second column displays the time at which the item was captured, either in elapsed time<br />

or clock time. By default, DebugView shows the number of seconds since the first debug<br />

record in the display was captured, with the first item always being 0.00. This can be helpful<br />

when debugging timing-related problems. This timer is reset when the display is cleared.<br />

Choose Clock Time from the Options menu if you prefer that the local clock time be displayed<br />

instead. Additionally, choose Show Milliseconds from the Options menu if you want<br />

the time stamp to show that level of granularity. You can also configure the time display with<br />

command-line options: /o to display clock time, /om to display clock time with milliseconds,<br />

and /on to show elapsed time.<br />

Tip Changing the Show Milliseconds setting doesn’t change the display of existing entries.<br />

You can refresh these entries by pressing Ctrl+T twice to toggle Clock Time off and back on. All<br />

entries will then reflect the new setting for Show Milliseconds.<br />

The debug output is in the Debug Print column. For user-mode debug output, the process<br />

ID (PID) of the process that generated the output appears in square brackets, followed by the<br />

output itself. If you don’t want the PID in the display, disable the Win32 PIDs option in the<br />

Options menu.<br />

You can select one or more rows of debug output and copy them to the <strong>Windows</strong> clipboard<br />

by pressing Ctrl+C. DebugView supports standard <strong>Windows</strong> methods of selecting multiple<br />

rows such as holding down Shift while pressing the Up or Down arrow keys to select<br />

consecutive rows, or holding down Ctrl while clicking nonconsecutive rows.<br />

By default, the Force Carriage Returns option is enabled, which displays every string passed<br />

to a debug output function on a separate line, whether or not that text is terminated with a<br />

carriage return. If you disable that option in the Options menu, DebugView buffers output<br />

text in memory and adds it to the display only when a carriage return is encountered or the<br />

memory buffer is filled (approximately 4192 characters). This allows applications and drivers<br />

to build output lines with multiple invocations of debug output functions. However, if output<br />

is being generated from more than one process, the output can be jumbled together, and<br />

the PID that appears on the line will be that of the process that output a carriage return or<br />

filled the buffer.<br />

If the text of any column is too wide for that column, move the mouse over it and the full<br />

text will appear in a tooltip.<br />

Debug output is added to the end of the list as it is produced. DebugView’s Autoscroll<br />

feature (which is off by default) scrolls the display as new debug output is captured so that<br />

the most recent entry is visible. To toggle Autoscroll on and off, press Ctrl+A or click the<br />

Autoscroll icon in the toolbar.<br />

www.it-ebooks.info

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!