Would you be interested in a live chat session on debugging techniques?

We’ve been thinking about hosting a live group chat session to talk with the debugging community.  If we had such a chat, the discussion would focus on debugging techniques and any questions you may have about anything we’ve previously blogged about.  If you’d be interested in participating in a chat session, please answer the survey question below.  Also, feel free to leave a comment on this page if there’s a particular debugging topic you would like for us to cover in the chat.


Thanks everyone for your feedback! This survey is now closed.

Comments (9)

  1. HKB says:

    Personally i would be interested in effective ways of debugging Memory Corruption problems as these just often point to random internal memory related operations in the kernel because of the Memory already being corrupt. As soon as physical memory checks out often the only thing i do is using Driver Verifier to check all Drivers.

    With many PC’s having 50-60 drivers and Driver Verifier only being effective with a few Drivers at a time such problems are painstakingly slow to debug. Especially since Memory Corruption problems often can take a long time to reveal themselves.

    I’m fairly new to debugging but say that you have captured 4-5 kernel-memory dumps, are there any effective tips on how to narrow down the problem?

  2. Chuck S. says:

    debugging with minidump files from Windows Error Reporting

  3. Madhur Ahuja says:

    I would be really interested in that ….

  4. steve says:

    I am a newbie to debugging but I am interested in  this.

  5. NickV says:

    How to troubleshoot Pool Corruption.

  6. rtshiva says:

    Count me in too, I would like to suggest scenarios where default !analyze -v points to a incorrect binary/module or a module that wasn’t the original cause of the crash.

  7. lkacso says:

    Yes definetly.Every aspect of debugging is interesting for me.

  8. jon_pfeffer@yahoo.com says:

    Yes, I am interested in acurately determining local variable values (when you do have matching public and private symbols)in optimized release builds. The applications of interest for debugging are unmanaged VC++ (VS2005 or later).

Skip to main content