搜索论坛 帖子排序:  Oldest to newest Newest to oldest

2006-09-12, 12:40 下午 土豆泥 注册: 2006-04-07 发 贴: 59 启用Windows内核驱动程序的调试输出 转载自微软网站。 How to enable verbose debug tracing in various drivers and subsystems View products that this article applies to. function loadTOCNode(){} Article ID : 314743 Last Review : September 27, 2005 Revision : 5.0 This article was previously published under Q314743 On This Page SUMMARY MORE INFORMATION Video miniport debugging 1394 debugging USB debugging PCI debugging PCMCIA debugging NDIS debugging Storage driver debugging Printer driver debugging User mode Kernel mode Audio driver debugging HID driver debugging Serial driver debugging Modem driver debugging Device installation debugging Notes var sectionFilter = "type != 'notice' && type != 'securedata' && type != 'querywords'"; var tocArrow = "/library/images/support/kbgraphics/public/en-us/downarrow.gif"; var depthLimit = 10; var depth3Limit = 10; var depth4Limit = 5; var depth5Limit = 3; var tocEntryMinimum = 1; .toc{display: none;} SUMMARY loadTOCNode(1, 'summary'); When you debug device drivers, it is important that you receive verbose debug tracing from the drivers and related subsystems. Most of the Microsoft-provided drivers and subsystems use global variables and a predefined set of values to control the verbosity of the debug tracing information that is sent to the debugger. This article discusses the following topics: • How to enable and control the debug tracing level by using a kernel debugger and registry values. • For a certain class of drivers, you can use the corresponding debugger extensions to enable and control debug tracing. • The differences between enabling debug tracing in Windows 2000 and Windows XP. Back to the top MORE INFORMATION loadTOCNode(1, 'moreinformation'); Important This article contains information about running .chk files for development and testing purposes. Microsoft Product Support Services (PSS) does not support production systems that have .chk files installed unless you were told by PSS to install the .chk files to isolate a problem. Before you install .chk files on a production system, make sure to back up the system, and make sure that you understand how to restore the replaced file if a problem occurs. For more information about .chk files, click the following article numbers to view the articles in the Microsoft Knowledge Base: 103659 (http://support.microsoft.com/kb/103659/) Setup hangs while inspecting hardware; how to use Ntdetect.com 320040 (http://support.microsoft.com/kb/320040/) How to use Ntdetect.chk to identify hardware problems in Windows 2000 For information about how to back up and restore the system, view Windows 2000 Help and support. For more information about NTbackups, click the following article numbers to view the articles in the Microsoft Knowledge Base: 240363 (http://support.microsoft.com/kb/240363/) How to use the Backup program to back up and restore the system state in Windows 2000 You can also contact your backup product provider for information about how to use their product. Note The following debugging information is subject to change at any time and is intended only for driver-debugging purposes. Also note that debug information may not be particularly useful to anyone other than developers. Back to the top Video miniport debugging loadTOCNode(2, 'moreinformation'); Note the following about video miniport debugging: • It requires checked build video port and miniport drivers. • It does not use a debugger extension. • It enables debug tracing by setting the global variable (or variables). • Variable names in Windows 2000 are different from those in Windows XP. • In Windows 2000, you can enable debug tracing either through the registry or the debugger, as follows: • Set the value of VideoDebugLevel (0-3) in the registry, as follows: HKEY_LOCAL_MACHINE\SYSTEM\CCS\Services\DriverName\DeviceN VideoDebugLevel:REG_DWORD: 2 • Or through the debugger, as follows: ed videoprt!VideoDebugLevel 2 • The video port on a Windows XP-based computer uses the new DbgPrintEx function (see the "NOTES" section of this article). The following variables are defined for video drivers: Kd_IHVVIDEO_Mask Kd_VIDEO_Mask Kd_VIDEOPRT_Mask To set a mask, do the following: • Add the mask that you want in the registry. For example: HKEY_LOCAL_MACHINE\SYSTEM\CCS\Control\Session Manager\Debug Print Filter “IHVVIDEO”=DWORD: 0xffffffff • Or in the debugger, as follows: ed Kd_IHVVIDEO_Mask 0xffffffff Back to the top 1394 debugging loadTOCNode(2, 'moreinformation'); Note the following about 1394 debugging: • It requires a checked build system or checked build 1394 modules. • On both Windows 2000 and Windows XP-based systems, set the corresponding global variable through the debugger. For example: ed ohci1394!ohcidebuglevel 6   Module name     Debug symbol   Range OHCI1394.SYS ohcidebuglevel 1-6 SBP2PORT.SYS sbp2debuglevel 1-4 1394BUS.SYS busdebuglevel 1-5 For more information, click the following article number to view the article in the Microsoft Knowledge Base: 259855 (http://support.microsoft.com/kb/259855/) How to enable debug prints in IEEE 1394 drivers Back to the top USB debugging loadTOCNode(2, 'moreinformation'); Note the following about universal serial bus (USB) debugging: • It requires a checked build system or checked build USB modules. • On a Windows 2000-based system, you need to set the corresponding global variable through the debugger. For example: ed USBD!USBD_Debug_Trace_Level 2   Module name     Debug symbol   Range UHCD.SYS UHCD_Debug_Trace_Level 0-2 OPENHCI.SYS OHCI_Debug_Trace_Level 0-2 USBHUB.SYS USBH_Debug_Trace_Level 0-3 USBD.SYS USBD_Debug_Trace_Level 0-3 • Use the following parameters on a Windows XP-based system.   Module name     Debug symbol   Range USBPORT.SYS USBPORT_Debug_Trace_Level 0-4 USBCCGP.SYS DbgVerbose 0 or 1 USBHUB.SYS USBH_Debug_Trace_Level 0-3 USBD.SYS USBD_Debug_Trace_Level 0-3 USBPORT.SYS USBPORT_CatcTrapEnable 0-1 • All USB miniport drivers use USBPORT for debug output. Back to the top PCI debugging loadTOCNode(2, 'moreinformation'); Note the following about Peripheral Component Interconnect (PCI) debugging: • It requires a checked build system or a checked build PCI.SYS module. • On both Windows 2000 and Windows XP-based systems, set the corresponding global variable through the debugger. For example (with 0x3 being the most verbose: ed PCI!PciDebug 0x3   Module name     Debug symbol   Range PCI.SYS  PciDebug   0-3  Back to the top PCMCIA debugging loadTOCNode(2, 'moreinformation'); Note the following about PCMCIA debugging: • It requires a checked build system or a checked build pcmcia module. • On both Windows 2000 and Windows XP-based systems, set the corresponding global variable through the debugger. For example ed PCMCIA!PcmciaDebugMask 0xFFFFFFFF where: #define PCMCIA_DEBUG_ALL 0xFFFFFFFF #define PCMCIA_DEBUG_TUPLES 0x00000001 #define PCMCIA_DEBUG_ENABLE 0x00000002 #define PCMCIA_DEBUG_PARSE 0x00000004 #define PCMCIA_DUMP_CONFIG 0x00000008 #define PCMCIA_DEBUG_INFO 0x00000010 #define PCMCIA_DEBUG_IOCTL 0x00000020 #define PCMCIA_DEBUG_DPC 0x00000040 #define PCMCIA_DEBUG_ISR 0x00000080 #define PCMCIA_DEBUG_CANCEL 0x00000100 #define PCMCIA_DUMP_SOCKET 0x00000200 #define PCMCIA_READ_TUPLE 0x00000400 #define PCMCIA_SEARCH_PCI 0x00000800 #define PCMCIA_DEBUG_FAIL 0x00008000 #define PCMCIA_PCCARD_READY 0x00010000 #define PCMCIA_DEBUG_DETECT 0x00020000 #define PCMCIA_COUNTERS 0x00040000 #define PCMCIA_DEBUG_OVERRIDES 0x00080000 #define PCMCIA_DEBUG_IRQMASK 0x00100000   Module name     Debug symbol   Range PCMCIA.SYS  PcmciaDebugMask   0–FFFFFFFF  Back to the top NDIS debugging loadTOCNode(2, 'moreinformation'); Note the following about network driver interface specification (NDIS) debugging: • NDIS debugging requires a checked build NDIS. For additional information about how to enable NDIS debug tracing on Windows 2000 and later versions, visit the following Microsoft Developer Network (MSDN) Web site: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/network/hh/network/ndisdbg_c5eab170-7932-4e0b-98df-e81747221ca9.xml.asp (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/network/hh/network/ndisdbg_c5eab170-7932-4e0b-98df-e81747221ca9.xml.asp) Back to the top Storage driver debugging loadTOCNode(2, 'moreinformation'); Note the following about storage driver debugging: • It requires a checked build system or checked build storage modules. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 296225 (http://support.microsoft.com/kb/296225/) How to enable SCSIPORT debug logging Back to the top Printer driver debugging loadTOCNode(2, 'moreinformation'); Note the following about printer driver debugging. User mode loadTOCNode(3, 'moreinformation'); • Requires a checked build system or checked build printer driver components (unidrv or pscript). • Attach to either the printing application or the spooler process (spoolsv.exe), depending on whether you are debugging the user interface (UI) module or the rendering module. • For Unidrv debugging, use the following setting: ed unidrv!giDebugLevel 1 Kernel mode loadTOCNode(3, 'moreinformation'); • Run the gflags command, and then enable the following flag on spoolsv.exe: • Windows 2000: "Place Heap Allocation at end of pages" • Windows XP: "enable page heap" • Restart the spooler (net stop/start spooler). • Run verifier.exe on Win32K.sys to debug your printer driver. Back to the top Audio driver debugging loadTOCNode(2, 'moreinformation'); Note the following about audio driver debugging: • It requires a checked build system or checked build audio modules. • On both Windows 2000 and Windows XP-based systems, set the corresponding global variable through the debugger. For example: ed USBAUDIO!USBAudioDebugLevel 3    Module name        Debug symbol       Range   USBAUDIO.SYS USBAudioDebugLevel 0-3 SYSAUDIO.SYS SYSAUDIOTraceLevel 0-100 Back to the top HID driver debugging loadTOCNode(2, 'moreinformation'); Note the following about HID driver debugging: • It requires a checked build system or checked build HID modules. • On both Windows 2000 and Windows XP-based systems, set the corresponding global variable through the debugger. For example: ed HIDCLASS!dbgverbose 1    Module name        Debug symbol       Range   HIDUSB.SYS HIDUSB_DebugLevel 0-1 HIDCLASS.SYS dbgverbose 0-1 Back to the top Serial driver debugging loadTOCNode(2, 'moreinformation'); Note the following about serial driver debugging: • It requires a checked build system or checked build serial modules. • Serial.sys (on both Windows 2000 and Windows XP-based systems): • Set the DebugLevel value in the registry, as follows: HKLM\System\CCS\Services\Serial “DebugLevel”= REG_DWORD:0xFFFFFFFF Or set it through the debugger, as follows: ed Serial!SerialDebugLevel (0x00000000 – 0xFFFFFFFF) • Mask values are defined in the following directory: %DDKROOT%\src\kernel\serial\serial.h • Serenum.sys (on both Windows 2000 and Windows XP-based systems): • Set the DebugLevel value in the registry, as follows: HKEY_LOCAL_MACHINE\System\CCS\Services\Serenum “DebugLevel”= REG_DWORD:1FF • Mask values are defined in the following directory: %DDKROOT%\src\kernel\serenum\serenum.h Back to the top Modem driver debugging loadTOCNode(2, 'moreinformation'); To enable full unimodem verbose debugging on Windows 2000 and Windows XP-based systems, you need to have a checked build, and then do the following: 1. For everything except Mdminst.dll and Unimdm.tsp, add the following registry keys: • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Unimodem "DebugFlags"=dword:0000003f • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon "SFCDisable"=dword:00000001 • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Modem "DebugFlags"=dword:0000003f • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Modemcsa "DebugFlags"=dword:0000003f 2. For Mdminst.dll, copy Unimdm.ini into %windir%. The following is an example of a Unimdm.ini file: [ModemUI] ; DumpFlags: ; 00000001 DCB ; 00000002 MODEMSETTINGS ; 00000004 DEVCAPS DumpFlags=0x0000000f ; TraceFlags: ; 00000001 Warnings ; 00000002 Errors ; 00000004 General ; 00000008 Function trace TraceFlags=0x0000000f ; BreakFlags: ; 00000001 Break on validate ; 00000040 Break on process attach ; 00000100 Break on API enter BreakFlags=0x00000000 ;; -------------------------------------------------------------------- [Modem] ; DumpFlags: DumpFlags=0x0000000f ; TraceFlags: ; 00000001 Warnings ; 00000002 Errors ; 00000004 General ; 00000008 Function trace ; 00010000 Detection queries ; 00020000 Class installer trace TraceFlags=0x0003000f ; BreakFlags: ; 00000001 Break on validate ; 00000040 Break on process attach ; 00000100 Break on API enter BreakFlags=0x00000000 ;; -------------------------------------------------------------------- [SerialUI] ; DumpFlags: ; 00000001 DCB DumpFlags=0x00000000 ; TraceFlags: ; 00000001 Warnings ; 00000002 Errors ; 00000004 General ; 00000008 Function trace TraceFlags=0x00000000 ; BreakFlags: ; 00000001 Break on validate ; 00000040 Break on process attach ; 00000100 Break on API enter BreakFlags=0x00000000 ;; -------------------------------------------------------------------- [Unimdm] ; DumpFlags: DumpFlags=0x0000000f ; TraceFlags: ; 00000001 Warnings ; 00000002 Errors ; 00000004 General ; 00000008 Function trace ; 00010000 dwDeviceID related ; 00020000 hdLine related ; 00040000 hdCall related ; 00080000 pLineDev related ; 00100000 pModemInfo related TraceFlags=0x001f000f ; BreakFlags: ; 00000001 Break on validate ; 00000040 Break on process attach ; 00000080 Break on process detach ; 00000100 Break on API enter BreakFlags=0x00000000 3. For Unimdm.tsp debugging, add the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96D-E325-11CE-BFC1-08002BE10318}\device instance\Logging Back to the top Device installation debugging loadTOCNode(2, 'moreinformation'); To receive a verbose trace from kernel and usermode PNP manager on Windows XP and later versions, you have to obtain a checked build, and then run following code: ed NT!Kd_NTOSPNP_Mask 0xFFFFFFFF ed NT!Kd_PNPMGR_Mask 0xFFFFFFFF On Windows 2000, you can set global variable PnpEnumDebugLevel to 1 or 2 in the kernel debugger as follows: ed nt!PnpEnumDebugLevel 2 Back to the top Notes loadTOCNode(2, 'moreinformation'); Some of the drivers and subsystems on Windows XP-based systems use the new DbgPrintEx function: ULONG DbgPrintEx(IN ULONG ComponentID, IN ULONG Level, IN PCHAR Format, . . . . [arguments]); Microsoft has defined about 95 different component IDs (look for DPFLTR_TYPE in the Ntddk.h file). For every component filter ID, there is a global mask variable, for example, NT! Kd_IHVVIDEO_Mask, NT!Kd_IHVAUDIO_Mask You can set the value of the mask either through the registry, as follows: HKEY_LOCAL_MACHINE\SYSTEM\CCS\Control\Session Manager\Debug Print Filter “IHV_AUDIO”=REG_DWORD:0xFFFFFFFF or with a debugger, for example, ed NT!Kd_IHVAUDIO_Mask 0xffffffff Debug output is filtered based on the global mask (Kd_Win2000_Mask) and the component level mask. The Windbg Help file documents how the mask and level values are used in filtering the output. To enable debug tracing, use the following code to locate your component ID either from the Ntddk.h file or from the debugger: x NT!Kd_*_Mask Then, set the value to the maximum for verbose output (0xffffffff). Currently, only a few classes of drivers (described in the "More Information" section of this article) use this new function. Back to the top APPLIES TO • Microsoft Windows XP Driver Development Kit • Microsoft Win32 Device Driver Kit for Windows 2000 • Microsoft Windows 2000 Professional Edition • Microsoft Windows 2000 Server • Microsoft Windows 2000 Datacenter Server • Microsoft Windows 2000 Advanced Server • Microsoft Windows XP Home Edition • Microsoft Windows XP Professional Back to the top Keywords:  kbhowto kbinfo kbbug kbkmode kbwdm kbplugplay kbinput kbndis kbfile kbdebug kbserial kbusb kbdisplay KB314743 Back to the top IP 地址: 已记录   报告

2006-09-12, 12:51 下午 土豆泥 注册: 2006-04-07 发 贴: 59 Re: 启用Windows内核驱动程序的调试输出 HOW TO: Enable Logging of Wiadebug.log in Windows XP http://support.microsoft.com/kb/307001/en-us How to enable debug prints in IEEE 1394 drivers How to enable NDIS debug tracing http://support.microsoft.com/kb/164459/en-us IP 地址: 已记录   报告

高端调试 » 软件调试 » Windows内核调试 » 启用Windows内核驱动程序的调试输出

请选择 论坛首页 |- 论坛搜索 |- 热门主题 |- 未回复的主题 用户选项 |- 登录 |- 注册 |- 找回密码 软件调试 |- Windows内核调试 |- C/C++本地代码调试 |- .Net程序调试 |- 脚本程序调试 |- Java程序调试 |- Linux内核调试 |- 《程序员》杂志调试专栏 |- WinDbg |- GDB |- 远程调试 |- 调试ACPI和BIOS |- 特殊的调试任务 |- 转储分析 |- GDK7 内核探秘 |- Windows内核 |- Linux内核 系统架构 |- CPU架构 |- PCI/PCI Express架构 程序人生 |- 软件物语 |- 社区活动 |- 名人逸事 联盟论坛 |- 欢迎使用CnForums 没有银弹 |- BUG也精彩 |- 豆腐工程 |- 软件圈里十大怪 Windows Vista |- 用调试利剑剖析VISTA内幕 |- 老专家如何破解新问题 |- 我的电脑谁说了算？ |- 资源 Office开发 |- Visio 驱动程序开发 |- Windows驱动开发 |- Linux驱动开发 |- Windows CE驱动开发 用户态开发 |- Windows本地代码（native）高级开发 |- Web应用开发 |- WinFX和.Net |- Office开发 本站建设 |- 高端调试团队 |- 版面布局 |- 活动建议 |- 网站维护 64位计算 |- 64-bit Windows |- 64-bit CPU 图书 |- 《软件调试》的示例程序 |- 《软件调试》的工具 |- 《软件调试》书友 |- 《软件调试》答疑 |- 《软件调试》勘误和意见 |- 《格蠹汇编》 |- 《软件调试》第二版卷1 |- 《软件调试》第二版卷2 云计算 |- IaaS |- 云存储 |- 大数据 |- PaaS和SaaS GPU |- CUDA |- OpenCL |- HSA |- 游戏开发与调试