Defrag Tools #169 - Debugging Tools for Windows Team

Sign in to queue

The Discussion

  • User profile image
    svenkat9

    Always a pleasure to listen to Andrew & Bill Messmer on debugging stuff. I remember Bill's two part series on dx command. It will be great, if you can do a session on NatVis and LINQ for those who are new to them (like me - Or, please point to any video sessions if any. The MSDN page has too much info on this).

  • User profile image
    s3curity​Consult

    @Johnson Rogers:Thank you for entertaining me this morning, however he is not a lizard, He is a debugger, Hillary is the lizard goodbye

     

  • User profile image
    aluhrs13

    @svenkat9: Defrag Tools #138 and #139 cover the basic of NatVis, is there anything specific you think are missing with NatVis? I'm also writing a blog post right now on the basics of constructing a LINQ query that I'll post on our blog soon (link also in video description).

  • User profile image
    svenkat9

    @aluhrs13:Thanks for your response. Yeah, a detailed blog on constructing LINQ queries, specifically in the context of WinDBG would be very helpful. I agree that 138/139 touched upon Natvis, but you will notice that @wmessmer: says that lot of details are in MSDN. MSDN details are too overwhelming when one is looking to quickly grab the concept in the context of WinDBG. Thanks, again!

  • User profile image
    aluhrs13
  • User profile image
    mcmurm

    @AndrewRichards Think you'll resurrect the !exqueue extension for Win 8 and newer? Looks like you guys did a lot of work in the _enode structure between Win 7 and Win 8 that the extension no longer plays nicely with.

    If you're not going to fix it, do you have a consistent way of dumping the system worker threads?

    Awesome topic and thanks in advance.

  • User profile image
    Aaron

    Hey guys,

    Would you be able to maybe dig into a kernel dump caused by NMI dumps? Sometimes I run into servers that we need to NMI dump / reboot, but windbg always points to NMI being the issue when it's just how we rebooted the server.

    Thanks!

Add Your 2 Cents