windbgtips (@windbgtips) header
windbgtips (@windbgtips) profile picture

A collection of some tips & tricks for the world's best debugger

Know a cool trick ? Send me a DM !
Joined November 2018
Photo by windbgtips (@windbgtips)Photo by windbgtips (@windbgtips)Photo by windbgtips (@windbgtips)Photo by windbgtips (@windbgtips)Photo by windbgtips (@windbgtips)Photo by windbgtips (@windbgtips)Photo by windbgtips (@windbgtips)Photo by windbgtips (@windbgtips)Photo by windbgtips (@windbgtips)Photo by windbgtips (@windbgtips)
If you update WinDbg today (1.2504.15001.0), you might notice another icon in the View tab of the ribbon, one called "Parallel Stacks". While incredibly useful in its own right, this isn't just a parallel stacks view. It's the introduction of graph visualization for extensions!
4
59
2
174
21,167
Well... It's not quite KD, but WinDbg has supported debugging the Linux kernel via an EXDI connection for some time. Easiest setup is to enable the gdbserver on QEMU and use EXDI in WinDbg selecting "Linux" as the OS. I've source level stepped the Linux kernel doing that...
3
13
42
4,933
windbgtips retweeted
It's been a minute since we have released a new version of TTD! New version is now available (1.11.410) which fixes module selective recording, enables large queries via .Calls() and fixes some emulator bugs reported by our customers. aka.ms/ttd
13
1
26
3,923
windbgtips retweeted
I know I'll catch flack for not knowing this, but the Mex WinDbg extension is so cool! During dynamic analysis I needed to grab the exact version of a module from a target but didn't want to resume execution to fetch it since hitting the breakpoint was tricky. !writemodule FTW!
3
8
1
86
10,342
If you spin your gdbserver with --multi (e.g.: gdbserver --multi localhost:1234), you can connect to it via the "Connect to Process Server" (same protocol string) and then see the process list and attach...
1
1
10
2,550
You can even tell us how to pull sources automatically from GitHub for your source level debugging... !addsourcemap <module> <local spec> <remote spec> as highlighted below. The db77...1c13 is the commit on master from which I built vim for this example.
2
7
1
33
8,843
Once you've connected, things should work very similarly to what you expect debugging a live Windows process. You can set breakpoints, single step, get locals, etc...
2
4
25
4,155
If you've ever wanted to live debug user mode Linux processes (e.g.: in WSL) from WinDbg, with 1.2402.24001.0, you can! Start up a gdbserver in WSL (e.g.: gdbserver localhost:1234 ./vim) and connect to it via WinDbg's "Connect to remote debugger"
12
95
9
302
81,877
windbgtips retweeted
I'm starting a series of WinDbg tutorial videos starting with the absolute basics. The first two videos cover how to install WinDbg and how to start a debugging session. augmend.com/replay/886e1f26-… augmend.com/replay/8e1ecc05-…
6
101
3
336
31,286
windbgtips retweeted
Here is a small WinDbg extension written in Rust 🦀 I am hoping it can serve as a template for people to get started 💪 github.com/0vercl0k/snapshot
3
39
2
175
12,865
windbgtips retweeted
Example (just record msvcrt.dll): ttd.exe -module msvcrt.dll ping.exe
2
4
11
2,854
Thanks to @_hugsy_'s contributions, the kdmp-parser library is now available on PyPI and also supports the new kernel dump types (8, 9, 10) that appeared in WinDbg around ~2022 😱 Go check it out: github.com/0vercl0k/kdmp-par… / pypi.org/project/kdmp-parser… 🔥
10
44
4,479
windbgtips retweeted
WinDbgX tip: If you press Ctrl+Shift+B, you can open a hex viewer for a file. The data is virtualized so that it can handle any size file. Like this 334MB Windows.UI.Xaml.pdb file. It's somewhat undocumented because it was just a test bed for the memory window, but still useful.
3
12
74
7,475
📢 @_hugsy_ added Python (>=3.8) bindings to udmp-parser (github.com/0vercl0k/udmp-par…) and we think they are ready for testing! Go try them out 🔥 pypi.org/project/udmp-parser…
1
8
23
6,514
windbgtips retweeted
Check it out! WinDbg has just released out of preview, out of the Windows store and (what I worked on) with Time Travel Debugging support for ARM64. aka.ms/windbg
2
44
4
142
29,504
WinDbg tip of the day: !chksvctbl -v Prints all NT system calls, their indexes and addresses @windbgtips
1
36
1
206
For those of you asking about the "Symbol Builder" sample being used in conjunction with existing public symbols... It's here! ... Or at least an initial level of that functionality is out for a pull-request on GitHub today (github.com/microsoft/WinDbg-…)
1
5
14
windbgtips retweeted
WinDbg tip: You can prefix a variable name with "$!" to tell the debugger that you only want to look for local variables. Otherwise, it assumes it could be a global variable and may try to download symbols for every loaded module. This works for ??, dx, and the watch window
1
11
69
windbgtips retweeted
New version of WinDbg just released, update now! This is a big release that we're very proud of. Lots of new features and bug fixes, including support for editing data in the memory window! More notes on changes in the UI below. apps.microsoft.com/store/det…
10
86
5
263
windbgtips retweeted
I have questions
1
4
27