NT SERIAL TAGS SERIAL
The target TCP IP port of the emulated serial COM port. For more information, see Setting Up a Serial Connection Manually. This can be in the format "com2" or in the format "\\.\com2", but should not simply be a number. For more information, see Setting Up a USB 3.0 Connection Manually and Setting Up a USB 2.0 Connection Manually. This must match the string specified with the /targetname boot option. This can only be specified through the command line or the environment variables, not through the WinDbg graphical interface.Ī USB connection string. If it is omitted, the debugger will default to the protocol appropriate for the current target computer.
NT SERIAL TAGS WINDOWS
If the target computer is running Windows Server 2003 or later, 1394Protocol should be set equal to "instance". If you wish to set this manually, and the target computer is running Windows XP, 1394Protocol should be set equal to "channel". This can almost always be omitted, because the debugger will automatically choose the correct protocol. The connection protocol to be used for the 1394 kernel connection. For more information, see Setting Up a 1394 Connection Manually. 1394Channel must match the number used by the target computer, but does not depend on the physical 1394 port chosen on the adapter. Valid channel numbers are any integer between 0 and 62, inclusive. To use the machine name, the DNS system on the network must have the machine name associated with the IP address of the target PC. The OFFER packets allow the debugger to connect to the host when no target= IP address is specified.įor more information on configuring the host IP address on the target, see Setting Up KDNET Network Kernel Debugging Automatically and Setting Up KDNET Network Kernel Debugging Manually. When the target is configured with a host IP address, it will send OFFER packets to the host every three seconds. When the target is configured with a host IP address, and the debugger is being run on the machine with the configured host IP address, there is no need to specify the target= IP address parameter. This allows you to take control of the debugging session away from an existing debugging connection. If the connection is successful, the target will drop any existing connection, and communicate only with this instance of the debugger. The debugger will send packets to the target repeatedly approximately every half second, attempting to connect. When the target= IP address is specified, this causes the debugger to initiate a connection to the specified target machine, by sending a special packet to the target, that will cause it to attempt to connect with that debugger. For more information, see Setting Up a Network Connection Manually. We recommend that you use an automatically generated key, which is provided by bcdedit when you configure the target computer. The encryption key to use for network debugging. You can choose any number from 49152 through 65535. For more information, see Symbol Path.Ī port number to use for network debugging. Directories in the list are separated by semicolons. ParametersĪ list of directories where symbol files are located. Use the following variables to specify a serial connection.įor more information, see Kernel-Mode Environment Variables. Environment Variablesįor debugging over a serial (COM port) or 1394 connection, you can use environment variables to specify the connection settings. Windbg -k com:pipe,port=\\ VMHost\pipe\ PipeNameįor more information, see WinDbg Command-Line Options. Windbg -k com:ipport= SerialTcpIpPort,port= SerialIPAddress Windbg -k com:port= ComPort,baud= BaudRate In a Command Prompt window, you can initiate a kernel-mode debugging session when you launch WinDbg. For more information about the dialog box and its entries, see File | Kernel Debug. Each tab specifies a different connection method. When the Kernel Debugging dialog box appears, click the appropriate tab: NET, 1394, USB, COM, or Local. When WinDbg is in dormant mode, you can begin a kernel debugging session by choosing Kernel Debug from the File menu or by pressing CTRL+K. There are two ways you can use WinDbg to initiate a live kernel-mode debugging session.
0 kommentar(er)
