| UID | title | description | old-location | tech.root | ms.date | keywords | ms.keywords | req.header | req.include-header | req.target-type | req.target-min-winverclnt | req.target-min-winversvr | req.kmdf-ver | req.umdf-ver | req.ddi-compliance | req.unicode-ansi | req.idl | req.max-support | req.namespace | req.assembly | req.type-library | req.lib | req.dll | req.irql | targetos | req.typenames | f1_keywords | topic_type | api_type | api_location | api_name | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NF:dbgeng.IDebugControl4.OutputVaListWide |
IDebugControl4::OutputVaListWide (dbgeng.h) |
The OutputVaListWide method formats a string and sends the result to the output callbacks that are registered with the engine's clients. |
debugger\outputvalistwide.htm |
debugger |
05/03/2018 |
|
IDebugControl4 interface [Windows Debugging],OutputVaListWide method, IDebugControl4.OutputVaListWide, IDebugControl4::OutputVaListWide, OutputVaListWide, OutputVaListWide method [Windows Debugging], OutputVaListWide method [Windows Debugging],IDebugControl4 interface, dbgeng/IDebugControl4::OutputVaListWide, debugger.outputvalistwide |
dbgeng.h |
Dbgeng.h, Stdarg.h |
Desktop |
Windows |
|
|
|
|
|
The OutputVaListWide method formats a string and sends the result to the output callbacks that are registered with the engine's clients.
Specifies the output-type bit field. See DEBUG_OUTPUT_XXX for possible values.
Specifies the format string, as in printf. Typically, conversion characters work exactly as they do in C. For the floating-point conversion characters, the 64-bit argument is interpreted as a 32-bit floating-point number unless the l modifier is used.
The %p conversion character is supported, but it represents a pointer in a target's address space. It might not have any modifiers, and it uses the debugger's internal address formatting. The following additional conversion characters are supported.
| Character | Argument type | Argument | Text printed |
|---|---|---|---|
| %p | ULONG64 | Pointer in an address space. | The value of the pointer. |
| %N | DWORD_PTR (32 or 64 bits, depending on the host's architecture) | Pointer in the host's virtual address space. | The value of the pointer. (This is equivalent to the standard C %p character.) |
| %I | ULONG64 | Any 64-bit value. | The specified value. If this is greater than 0xFFFFFFFF, it is printed as a 64-bit value; otherwise, it is printed as a 32-bit value. |
| %ma | ULONG64 | Address of a NULL-terminated ASCII string in the process's virtual address space. | The specified string. |
| %mu | ULONG64 | Address of a NULL-terminated Unicode string in the process's virtual address space. | The specified string. |
| %msa | ULONG64 | Address of an ANSI_STRING structure in the process's virtual address space. | The specified string. |
| %msu | ULONG64 | Address of a UNICODE_STRING structure in the process's virtual address space. | The specified string. |
| %y | ULONG64 | Address in the process's virtual address space of an item with symbol information. | String that contains the name of the specified symbol (and displacement, if any). |
| %ly | ULONG64 | Address in the process's virtual address space of an item with symbol information. | String that contains the name of the specified symbol (and displacement, if any), as well as any available source line information. |
Specifies additional parameters that represent values to be inserted into the output during formatting. Args must be initialized using va_start. This method does not call va_end.
This method may also return error values. See Return Values for more details.
| Return code | Description |
|---|---|
|
The method was successful. |
When generating very large output strings, it is possible to reach the limits of the debugger engine or of the operating system. For example, some versions of the debugger engine have a 16K character limit for a single output. If you find that very large output is getting truncated, you might need to split your output into multiple requests.