In this episode of Defrag Tools, Andrew Richards talks to Andy Luhrs and Bill Messmer from the Debugging Tools for Windows team. We talk about the new JavaScript extensibility and scripting abilities in WinDbg available in the WDK and SDK build 14951 and newer. Blog - https://blogs.msdn.microsoft.com/windbg/Email - [email protected] Bill leveraged the debugger object model previously in these episodes: Defrag Tools #138 - Debugging - 'dx' Command Part 1Defrag Tools #139 - Debugging - 'dx' Command Part 2Defrag Tools #169 - Debugging Tools for Windows TeamTimeline: [00:00] Welcome and introductions[00:24] New SDK drop[00:29] Why JavaScript[02:07] New commands[03:50] Visual Studio Code[04:00] Example - Hello World[07:15] Debugger default namespaces[09:07] Example - Print all threads[10:26] Example - Conditional breakpoint[18:13] 'g' vs. 'gc' – Andrew was right! 'gc' resumes execution in the same way that it started. So if you hit 'p' and then hit a conditional breakpoint that has 'gc' in it, the 'gc' will just finish your initial 'p'.[20:40] Example - Unique stacks[34:40] Example - Addition Questions/Comments? Email us at [email protected] JavaScript MSDN Docs: JavaScript Debugger ScriptingJavaScript Debugger Example ScriptsNative Debugger Objects in JavaScript Extensions Unique Stacks Example (the right one):

"use strict";

class __stackEntry

{

constructor(frameString) {

this.threads = [];

this.frameString = frameString;

this.children = new Map();

}

display(indent)

{

for (var child of this.children.values())

{

host.diagnostics.debugLog(indent, child.frameString, " [Threads In Branch: ");

for (var thread of child.threads)

{

host.diagnostics.debugLog(thread.Id, " ");

}

host.diagnostics.debugLog("]\n");

child.display(indent + " ");