WinDbg不同版本间的主要差异

全面讲解x64与ARM64平台下WinDbg符号加载差异 深入对比x64和ARM64平台下WinDbg符号加载机制的不同,结合windbg分析蓝屏教程实战场景,帮助开发者快速定位系统崩溃问题,提升调试效率。 阅读详情

近一两年来,WinDbg的版本更新差不多每月都有,这种速度也侧面证明了微软内部对WinDbg的重视,否则不会升级这么快吧?而且可以看出其发展是和微软的其它技术发展同步的。比如DotNet热时WinDbg的那几个版本加了很多对调试托管代码的支持,64位热时,WinDbg便加入对WOW64的支持。无疑微软的很多内部团队也在使用WinDbg做调试。当他们发现问题或有新的要求时就会让WinDbg改正或加入。

版本升级这么快,有时真的不知道每个版本到底有什么变化,该不该升级?还好微软的站点上有一个简单的列表关于每个版本的变化。但这个LISt已经不包括6.2以前的版本(大约是05年3月)了。说不定现在包括的版本过几个月也不见了。赶紧贴过来吧!

Highlights in Version 6.6.3.5

The following changes have been made to Debugging Tools for Windows:

•

New UI enhancements

•

Right-click copy support in watch/locals window

•

Source syntax coloring

•

MDI emulation mode

•

Hover evaluation when a syntax parser is available for a source file

•

Added kd connection property page for USB 2.0

•

New options in Resolve Unqualified Symbols in the Debug Menu

•

New Copy Formatted command in the Edit menu for copying rich text

•

New -ui command line options

•

Equivalent to -premote added to Connect in File menu

•

Updated appearance of styles and toolbars

•

Toggle QuickEdit Mode from Options in View menu

•

New Event Timestamps menu under the View menu

•

Enhanced docking options

•

Easier view of thread names

•

New Source Server features

•

Additional support for Subversion

•

Set which srcsrv.ini file to use via an environment variable

•

Additional Symbol Server support

•

Support for coexisting compressed and uncompressed files

•

!analyze enhancements

•

Initial support for plug-in analyzers

•

Enhancements for bugchecks, exceptions, hangs and /GS

•

New and updated extensions

•

in kdexts.dll: !process

•

in ntsdexts.dll: !htrace

•

updates to !token, !sd and !peb

•

New and updated commands: .dumpdebug, .frame, .ignore_wow_kd_context, .cmdtree, .cache, .readmem, .typeopt, .f+, .f-, .pagein, .idle_cmd, sxr, lse, pt, tt

•

New options for commands: bl, ld, .printf, .kill, .detatch, .abandon, bm, dt

•

New symproxy feature

•

Can use file pointers for http symbol stores

•

Better debugging

•

Better detection of WOW64 situations

•

Retrieval of non-running thread stacks

•

Improved functionality with psuedo-registers

For details of all the new features in Debugging Tools for Windows, consult the documentation. To access the documentation, click Start, point to Programs, and then click Debugging Tools for Windows. After the program opens, click Debugging Help.

Highlights in Version 6.5.3.8

The following changes have been made to Debugging Tools for Windows:

•

Compatibility updates for Windows codename "Longhorn."

•

New EngExtCpp C++ extension framework:

•

This is a Developer Preview, and APIs are subject to change.

•

Headers and samples can be installed by choosing the SDK component during installation of Debugging Tools for Windows.

•

Win9x user-mode compatibility fixes:

•

Requires MSLU. See debugger documentation for details.

•

Win9x debugging is still not a supported scenario.

•

USB 2.0 kernel debugging support. Requires a Windows "Longhorn" target computer and some additional software. See debugger documentation for details.

•

New tool available: DBH.

•

New commands available: .allow_image_mapping, .apply_dbp, .prompt_allow, .step_filter, and .suspend_ui.

•

New options available for the lm, uf, .attach, .cxr, .foreach, .opendump, and .printf commands.

•

All debuggers now support .wtitle.

•

New pseudo-register: $ea2.

•

New automatic aliases: $CurrentDumpArchiveFile, $CurrentDumpArchivePath, $CurrentDumpFile, $CurrentDumpPath, $ntsym, $ntnsym, and $ntwsym.

•

New extensions available:

•

in exts.dll: !bitcount.

•

in kdexts.dll:!sysinfo.

•

in wmitrace.dll: !buffer, !ckcl, !regtable, and !setprefix.

•

in wdfkd.dll: !wdfdevice, !wdfdevicequeues, !wdfdriverinfo, !wdfextendwatchdog, !wdfgetdriver, !wdfldr, !wdfqueue, !wdfrequest, !wdfsetdriver, and !wdftraceprtdebug.

•

New extension module fltkd.dll. This contains !cbd, !contextlist, !ctx, !filter, !filters, !fltobj, !frame, !frames, !instance, !irpctrl, !msgq, !namecachelist, !port, !portlist, !relobjs, !stats, !streamlist, !traceflags, !tracelevel, !tree, !volume, and !volumes.

•

New options available for the !search extension.

•

New symbol quoting syntax.

•

WinDbg UI changes, including:

•

"Edit->Clear Command Output" allows clearing partial text from command window.

•

"File->Open Executable" remembers process arguments and start directory.

•

Cascading and tiling of undocked windows.

•

Watch window and Locals window context option to invoke 'dt' command.

•

Source Server support for Subversion version control system.

•

Updated 1394 kernel debugging drivers.

•

Updates to many sections of the debugger documentation (debugger.chm).

•

New documentation file, Kernel_Debugging_Tutorial.doc, aimed at customers who are familiar with other debugging tools and want to learn how to use WinDbg for kernel debugging.

•

Many improvements to the !analyze extension.

•

Numerous fixes to bugs in various commands and extensions reported by customers.

For details of all the new features in Debugging Tools for Windows, consult the documentation. To access the documentation, click Start, point to Programs, and then click Debugging Tools for Windows. After the program opens, click Debugging Help.

Highlights in Version 6.4.7.2

The following changes have been made to Debugging Tools for Windows:

•

New SymProxy tool. See the details below.

•

New WinDbg UI Themes. These are preconfigured WinDbg workspaces that contain a useful configuration of debugging information windows. You can find documentation in Themes.doc.

•

New options for the wt and .printf commands. New options for the !Name2EE, !dumpstackobjects, !dumpobj, !dumpcollection, !dumpdomain, !eeheap, !dumpheap, !clrstack, !address, and !heap extensions. New "ReqHost" option for the TCP transport.

•

New commands: gc, .event_code, and .fnret. New extensions: !stl, !xpoolmap, !DumpField, !dumpacpi, !dumpcpuinfo, !dumpcpumicrocode, !dumpcpuspeed, !dumpmachineid, !dumpregisters, !dumpsmbios, !findstack, !dumpMethodSig, !DumpSig, !dumpRuntimeTypes, and !homedir. New pseudo-registers and functions: $fnsucc() and $retret64.

•

New extension module ks.dll, containing !allstreams, !automation, !devhdr, !dhdr, !dump, !dumpbag, !dumpcircuit, !dumplog, !dumpqueue, !enumdevobj, !enumdrvobj, !eval, !findlive, !forcedump, !graph, !help, !kshelp, !libexts, !objhdr, !ohdr, !pchelp, !pciaudio, !pciks, !shdr, and !topology.

•

Symbol server support for cascading downstream stores. You can now use multiple downstream stores to cache symbols sequentially. If one store is inaccessible, the chain is not broken.

SymProxy now allows you to create a single HTTP symbol server in your network to which all of your debuggers can point. This has the benefit of pointing to multiple symbol servers (both internal and external) with a single symbol path, handling authentication, and increasing performance through symbol caching. You can find documentation in symhttp.doc.

Highlights in Beta Version 6.4.4.4

The following changes have been made to Debugging Tools for Windows:

•

New tools, including AgeStore and rtlist.

•

New options for the e, g, s, x, .attach, .create, .dump, .logopen, .open, .process, .shell, .thread, and .time commands. The .restart command now works remotely. New options available for the !list extension.

•

New commands: dpa, dpu, ub, .extpath, .scroll_prefs, .flash_on_break, .sound_notify, !can_write_kdump, !GCHandleLeaks, !GCHandles, and !StopOnException.

•

WinDbg UI changes, including:

•

Memory Window: Dynamic column count auto fitting, line scrolling, and new display formats.

•

Watch/Locals Windows: "tab" switching, F2 to enter edit mode, and opening a memory window against variable entries.

•

Scratch Pad: For associating contents with a file.

•

Command Window: New coloring and text marking options, and history that can be opened from a file.

•

Closed windows that now retain their state.

•

User-loaded extensions that are saved in the workspace.

•

Many improvements to the !analyze extension.

•

Numerous bug fixes to various commands and extensions reported by customers.

Highlights in Version 6.3.17

The following changes have been made to Debugging Tools for Windows:

•

Support for the next generation of Microsoft Windows codenamed "Longhorn".

•

New user interface (UI) management capabilities in WinDbg.

•

Many improvements to the !analyze extension.

•

Improved extension interface documentation (debugext.chm). If you want to access this documentation or build debugger extensions, you should perform a custom install of Debugging Tools for Windows and select all features.

•

The ability to execute a series of debugger commands programmatically or create a more complicated "program" by using flow control. This allows you to conditionally execute commands or even pipe the output of one command into another. New control flow tokens include .foreach, .do, .for, .while, .if, .elsif, .else, .catch, .break, .continue, and .leave. Aliases are used as the "local variables" in these programs.

•

Multiple new options for setting aliases.

•

Numerous bug fixes to various commands and extensions reported by customers.

WinDbg now features enhanced UI management capabilities. Support for window docking, window tear-off, and window tabs has been added to allow users more flexibility in configuring the user interface.

Some features of the new WinDbg UI include:

•

Window docking
Windows that are part of the frame are "tied" to the frame, and stretch and shrink when the main debugger window frame is changed.

•

Window tear-off
WinDbg windows can "float" outside the frame and do not change or move when the main WinDbg frame is moved. Windows that are torn off the main frame are still child windows of WinDbg, and are minimized and maximized with the frame and do not show up on the task bar.

•

Window tabs
Docked windows can be tabbed together, allowing multiple windows to be layered while providing easy access to the windows under the currently visible one.

Tips for using the new WinDbg UI:

•

At startup, all WinDbg UI windows are in an "undocked" state. To dock the window, double-click it or drag it into the main WinDbg frame window.

•

To tab a window, drag the window to the other window to which you want to tab it, moving the mouse to the center of the window. Drop it when you see the outline of the dragged window match the frame of the other window. Switch between the tabbed windows by pressing CTRL+TAB.

For full details, see the Debugging Tools for Windows help file.

Highlights in Beta Version 6.3.5

The following changes have been made to Debugging Tools for Windows:

•

New support for managed code debugging that requires Windows codenamed "Longhorn".

•

Many improvements to the !analyze extension.

•

Internal debugger support for Unicode.

•

Numerous new options and many bug fixes in SymChk and SymStore.

•

New options for the bp, bm, bu, ba, dt, d, s, x, and .logopen commands. New options to DbEngPrx. New options to the !process and !thread extensions.

•

Numerous bug fixes to various commands and extensions reported by customers.

Highlights in Version 6.2.13.1

The following changes have been made to Debugging Tools for Windows:

•

New debugger extension interface documentation. To install this documentation, perform a custom install of the package and select all features.

•

New commands, including .send_file, .record_branches, .ignore_missing_pages, and .quit_lock, .ttime, .fpo.

•

New options to the dv command.

•

New d[d|q|p]p command that can walk one level of pointer indirection for data on the stack.

•

Numerous improved debugger extensions, including !chkimg, !exchain, !verifier, !runaway, and !vm.

•

New options for the SymChk and SymStore tools.

•

Updated IEEE 1394 debugging drivers.

•

x64 debugging updates.

•

Resolution of all reported bugs.

WinDbg Preview内存转储分类解析:不同模式对比说明 深入剖析WinDbg Preview中各类内存转储文件的差异与应用场景,帮助开发者精准选择调试模式。结合windbg preview的特性,提升问题定位效率,优化调试体验。 阅读详情

相关推荐

图解说明x64与ARM64下WinDbg!analyze -v结果差异

通过实例对比x64和ARM64架构中WinDbg!analyze -v的输出区别,深入解读蓝屏故障排查关键点,帮助开发者更好掌握windbg分析蓝屏教程中的核心技巧,提升跨平台调试能力。

weixin_36235398的博客 924

windbg 旧版使用

下载地址: 下载 Windows 调试工具 - WinDbg - Windows drivers | Microsoft Docs安装完成,会具有各种平台的windbg工具32位app,使用32位任务管理器生成转储文件。地址:C:\Windows\SysWOW64\Taskmgr.exe工具配置:file ->symbol file path 写 srv*c:/Symbols*https://msdl.microsoft.com/download/symbols;程序符号路径文件打开 转储文件。输入命令可能

qq_18607263的博客 1043

Windbg调试工具详细介绍

本文详细介绍一下Windbg的相关内容。

dvlinker的技术专栏 1万+

windbg preview下载及其历史版本下载

windbg preview下载及其历史版本下载

What If... 2160

Windbg 调试工具实用指南及版本选择

Windbg,全名Windows Debugger,是微软发布的一款强大的调试工具,广泛应用于软件开发及维护中,特别是在系统崩溃分析、内核调试、驱动开发等领域。它为用户提供了一个命令行界面,以及一个可选的图形用户界面(GUI)插件,可以针对Windows平台的本地应用程序、驱动程序以及硬件问题进行深入的诊断和调试。作为一个专业IT从业者,掌握Windbg是必不可少的技能之一。它支持多种语言和多种架构的调试,包含本地代码调试和脚本语言自动化调试。

weixin_30838971的博客 1216

windbg下载win7&8&8.1合集

将找到的windbg做了个整理,在win7或win8环境开发时适配Visual studio2013下了很多debugger,可以一次下载下来看哪个版本适配,下边是版本号及文件 dbg x86 6.3.9600.17298.msi dbg x86 6.11.1.404.msi dbg x86 6.12.2.633.msi

WinDbg安装入坑2(C#)

1 32位应用程序导出的Dump文件要用32位的WinDbg打开,想要没有那么多的问题,还得要求用32位的任务管理器导出Dump文件,32位的任务管理器的路径如下:C:\Windows\SysWOW64\taskmgr.exe。不管是使用.load C:\Windows\Microsoft.NET\Framework64\v4.0.30319\SOS.dll还是使用。可能是我们导入的sos版本不对,由于我们的应用程序是.net framework 3.5 的,可以试试。没有报错,再次输入!

zxy13826134783的博客 2158

windbg中文版(含32位64位原版)

windows蓝屏分析工具,可以分析windows蓝屏后生成的后缀DMP的文件,软件中文免安装,还附带原版英文32和64位。

WinDbg、Symbol Packages、SRVINSTW、DebugView下载地址

最新WinDbg (最新版V6.11.1.404 - March 27, 2009及部分历史版本)下载网页:http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx Symbol Packages文件下载网页http://www.microsoft.com/whdc/DevTools/Debugging/sym

kmlch的专栏 1734

windbg 中文版下载(替换原来版本文件就可以)

作用 本版本的Windows调试工具文档描述了4种Microsoft调试器:WinDbg,KD,CDB,NTSD和其他调试工具。 WinDbg, KD, CDB, 和 NTSD 调试器 这几款调试器完全支持在基于x86、Itanium、x64的处理器上运行,并且可以在所有基于NT内核的Windows操作系统上运行。它们可以调试操作系统以及在操作系统上运行的应用程序、服务和驱动程序。基于NT内核的操作系统包括: * Windows Vista * Windows Server 2003 * Windows XP * Windows 2000 CDB和NTSD在实质上是相同的。在这组文档中,所有提及“CDB”的地方,同时适用于CDB和NTSD,这两个调试器的所有不同点都会单独注明。获取更多信息,查看CDB和NTSD。 在Windows Vista的System32目录下有NTSD的一个拷贝。本文档中描述的Windows调试工具包中的NTSD可能和System32目录中的NTSD并不是同一个版本。

地瓜派RDK X5部署YOLOv11n避坑指南:手把手教你解决Softmax算子导致的性能暴跌问题

本文详细介绍了在地瓜派RDK X5开发板上部署YOLOv11n模型时遇到的性能问题及解决方案。通过强制BPU部署Softmax算子,成功将推理速度从7FPS提升至47FPS,并提供了完整的优化流程和技术细节,帮助开发者避免类似性能陷阱。

weixin_42629671的博客 269

ldb, gdb, windbg, vsjitdebugger, ollydbg 的差异

LLDB:适合 macOS 和 iOS 的调试,可以集成到 Xcode 中。GDB:适合 Linux 和 Unix 的调试,支持多种语言。WinDbg:适合 Windows 系统的调试,支持内核模式和用户模式。:适合 Visual Studio 环境下的托管代码调试。OllyDbg:适合逆向工程和恶意软件分析,有较好的反汇编功能。

qq_35374791的博客 1567

全志T133-s3(Tina Linux)下RTL8723DS WiFi驱动移植与调试实战

本文详细介绍了在全志T133-s3平台(Tina Linux)上移植RTL8723DS WiFi驱动的完整流程,包括硬件连接、驱动源码获取、内核配置、系统适配、设备树配置以及常见问题排查。通过实战案例,帮助开发者快速解决SDIO接口通信、固件加载、电源管理等关键问题,实现稳定的WiFi功能。

weixin_30505225的博客 508

WinDbg下载位置与版本选择:核心要点说明

想快速找到可靠的WinDbg下载渠道?别再被旧版或第三方捆绑包坑了。本文直击Windows调试工具的官方获取路径,详解Preview版与稳定版适用场景,兼顾WinDbg下载便捷性与环境兼容性,助你一步到位装对版本。

weixin_42186015的博客 310

NLPIR 汉语分词系统 (PyNLPIR) 学习手札

1 关于NLPIR最近在做一些NLP相关的任务,其中一个关键的子任务就是如何对汉语进行分词?关于分词的方式,有很多很多,也是很多学习者的练手任务(比如我们当时的期末作业就有这个)。但是,轮子还是要搬来用,自己写的分词只能说是去了解这个方式(了解某个算法),做出来的都是能看不能用,毕竟模型、算法、语料库等一座座大山等着我们攻克。所以,我找了一些资料,看到一个不错的教程,他用了NLPIR,所以我也跟着使

MebiuW的专栏 2万+

别再到处找教程了!Windows下用FFmpeg+Mediamtx+VLC搭建本地RTSP流媒体服务器,保姆级配置流程

本文详细介绍了在Windows系统下使用FFmpeg、Mediamtx和VLC搭建本地RTSP流媒体服务器的完整流程。从环境准备到核心配置,再到推流和拉流的实战技巧,提供了保姆级的避坑指南和优化建议,帮助开发者快速实现稳定的流媒体服务部署。

weixin_42614269的博客 213

windbg 调试学习

符号服务器地址 微软的公共符号服务器地址:Symbol information 五种符号加载状态 1. deferred: 延迟加载,现在还不需要使用这个模块的符号,将在后面需要的时候加载 2. no symbols: 没有找到相应的符号文件 3. export 4. public: 一般指使用服务器上的共有符号 5. private: 一般指使用本地的私有符号 符号相关的命令 1. 设置符号加载路径 注意: 访问微软的符号服务器可能需要梯子,注意用梯子的方式,要使..

momodeconger的博客 2701

UNext:基于 MLP 的快速医学图像分割网络

有代码,可深入学习轻量级分割模型的论文切入点 UNet 及其最新扩展(如 TransUNet)近年来一直是领先的医学图像分割方法。然而,这些网络无法有效地用于应用中的快速图像分割,因为它们参数繁重、计算复杂且使用缓慢。为此,我们提出了 UNeXt,它是一种基于卷积多层感知器(MLP)的图像分割网络。我们以有效的方式设计了 UNeXt,其中包括早期卷积阶段和潜在阶段的 MLP 阶段。我们提出了一个标记化的 MLP 块,我们可以在其中有效地标记和投影卷积特征,并使用 MLP 来对表示进行建模。

Philo的博客 3943

windbg:设置断点 bp, bu, bm

windbg 中断点设置

Mr.Sugarcane 2598

ComfyUI全自动换装工作流:从零到一的实战指南

本文提供了一份详细的ComfyUI全自动换装工作流实战指南。从环境配置、模型准备到核心工作流架构的逐步拆解,手把手教你搭建一条高效的AI换装流水线。文章深入解析了从输入、预处理、融合到输出的四步核心逻辑,并分享了关键参数调优与进阶技巧,旨在帮助电商从业者、内容创作者及AI爱好者轻松实现高质量、高效率的“一键换装”。

weixin_29198045的博客 902

Qt基础之十九:进程与QProcess

进程就是一个程序的执行实例,也就是正在运行的程序。对操作系统来说,进程就是一个担当分配系统资源CPU时间、内存的实体。在Qt 中,我们使用QProcess来表示一个进程。这个类可以允许我们的应用程序启动一个新的外部程序,并且与这个程序进行通讯。当外部程序开始启动时,QProcess的状态为Starting;外部程序已经启动时,QProcess的状态为Running,并发送started()信号;当外部层序退出了,QProcess的状态为NotRunning(初始状态),并发送finished()信号。

草上爬的博客 1万+

WinDbg 使用 !idt 命令

VMware中的是XP SP3, Host也是SP3. 当用WinDbg调试的时候, 总是说Symbols不对. 我想可能是由于虚拟机是单核, 而Host是超线程的原因吧, 导致Ntoskrnl的版本不同的原因吧.  删掉ntoskrnl.pdb文件夹, .reload, 成功了, 终于出现 Windows Internals(4th) 上说的那个结果了, 当然还

tsdn 2589

2025年06月中国电子学会青少年软件编程(图形化)等级考试试卷(三级)答案 + 解析

2025年06月中国电子学会青少年软件编程(图形化)等级考试试卷(三级)答案 + 解析

伶俐角少儿编程 345

Pwndbg与WinDbg Preview:现代Windows调试器对比

在漏洞开发与逆向工程领域,调试器的选择直接影响工作效率。2025年的今天,原生GDB/LLDB仍缺乏用户友好的内存转储命令,而WinDbg用户切换到Linux环境时往往无所适从。本文将从命令体系、内存分析、跨平台支持三个维度,对比Pwndbg(增强版GDB/LLDB)与WinDbg Preview的实战能力,帮助开发者选择最适合的调试工具链。 ## 命令体系对比 ### 兼容性设计差异 Pwn

gitblog_00556的博客 904

TMS_WebGMaps_1.9.8.0_Full_Source

TMS_WebGMaps_1.9.8.0_Full_Source 全源码 delphi cbuilder

霍尼韦尔SoftMaster使用说明

霍尼韦尔SoftMaster使用说明

WinDbg 定位句柄泄漏问题

文章目录一、观察进程是否有句柄泄漏1、查看工具任务管理器查看句柄数procexp.exe查看进程句柄信息2、判断是否有句柄泄漏二、定位方法1、WinDbg分析句柄泄漏1.1 Event句柄泄漏1.1.1 代码示例1.1.2 一、观察进程是否有句柄泄漏 1、查看工具 使用任务管理器或Process Explorer(procexp.exe)工具可观察进程的句柄数。 任务管理器查看句柄数 procexp.exe查看进程句柄信息 2、判断是否有句柄泄漏 通常在程序运行稳定后,再观察句柄数有无增长,比如进程启动5分

过好每一天的女胖子 4521

lwip-2.0.3

lwip是瑞典计算机科学院(SICS)的Adam Dunkels 开发的一个小型开源的TCP/IP协议栈。实现的重点是在保持TCP协议主要功能的基础上减少对RAM 的占用。

上一篇: Huffman编码的8种实现方式
下一篇: Windows应用程序调试必备的--符号文件(Symbols)
iiprogram
博客等级 码龄25年 1068粉丝 1515原创
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付:10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值