Reading the LogViewer Display
Collapse the table of content
Expand the table of content

Reading the LogViewer Display

LogViewer displays a list of all functions in the order they were logged.

Each row of the display contains several columns. The significance of each column is as follows.

ColumnMeaning

+/-

If this column contains a "+" (plus sign), it indicates that the function takes one or more parameters. To see the parameters and their values, either double-click the row or hit the right arrow key when the row is outlined in red. To hide it again, double click it again or hit the left arrow key when the row is outlined in red.

There is also a "d#" value in this column. This indicates the "depth" of the function call (in other words, how deep the call is nested in other logged function calls).

#

The sequential row number of the function call. This is useful when you have filters applied and are interested to know how far apart two function calls are.

Thrd

The thread number on which the function call was made. This number is not a thread ID, but is rather an assigned number based on the order that threads were created in the process.

Caller

The instruction address that made the function call. This is derived from the return address for the call. It is actually the return address minus 5 bytes (the typical size of a call dword ptr instruction).

Module

The module that contains the calling instruction.

API Function

The name of the function. The name of the module that contains the function is omitted for brevity.

Return Value

The value returned by the function, if it is not a void function.

 

Double-clicking on a row in the viewer will expand the row to reveal the parameters to the function and their values "going in" to the function. If they are designated as OUT parameters, their value "coming out" is shown on the right.

You can also use the ENTER key or the right and left arrow keys to expand and collapse rows.

Function calls that returned failure status codes are shaded in pink.

 

 

Send comments about this topic to Microsoft

Show:
© 2016 Microsoft