Andrew Richards

@Jack: Virtualization doesn't affect the Virtual Memory layout of processes (if it did, that'd be a worry actually).

A lot of it came down to time - both Chad and I are very busy in our day jobs and it got harder and harder to find the prep time. We also ran out of content that we do day-to-day. The big thing we never want/ed to do is present inaccurate information.

I'm tempted to tape a few episode on just some random dump debugging - for the fun of it. Would you like that?

It’s on hold/cancelled. We’ll tape new ones if a big topic turns up and someone else hasn’t covered it.

Stack Overflow is an interesting error type. It is handled in the kernel, rather than user mode -- primarily to block bad code (viruses, etc.) from handling the error, and moving on (i.e. keeping themselves hidden).

In this situation, WER does not give the AeDebugger the chance to be involved -- instead it takes the dump directly.

As a user, look at the .exr -1, .ecxr and k output.

!analyze does the same (via APIs) thing internally to decide what type of analysis to run.

You can jump to the "!analyze -v" output, if you want, and skip the other commands -- it's easier to understand the "!analyze -v" output if you have some context to base it on.

@eschwabe:!analyze considers the last exception record (it does it through the API : IDebugControl3::GetLastEventInformation) - you won't see it running the command.

If you ever find a case where !analyze doesn't seem to be considering it, email us and we'll look into it.

All of the new !black* commands are great to leverage for any hang related analysis.
The blackbox secondary streams are added by the hang bugcheck codes (E2, 1C8, etc.).
!analyze reads the data to aid decisions.

@Peter:Yes, the plan is to do more tools that aren't debugging based.

Debugging is lots of small topics - and that's what drove the show's creation.

Such an awesome team and workspace to tape in -- looking forward to taping many new episodes in 2018.

@j1n1:WinDbg doesn't have intrinsic CLR support... it's only by extensions (SOS, etc.).

Visual Studio does have intrinsic CLR support -- but doesn't currently support TTD.

BTW, USB-A is the rectangle connector. USB-B is the D connector in regular, mini (old cameras) and micro (phones) sizes, and USB-C is the new rectangular one with the rounded corners.

USB 2 requires a client and server, and thus uses A+B connectors.

USB 3 is bidirectional, allowing C at both ends. Most data cables are A to C though. Because C is both, that is why it can drive HDMI, etc.

 

@wellisolutions: It's the 2nd edition.