@voidp: Good idea. Added to the show notes.
OneDrive link for the PDE debugger extension: http://sdrv.ms/11C7S9c
@BrianCatlin: I was going to mention it but decided not to. You need to know what the schema is to use the tool effectively. Personally, I think writing the XML directly is as easy as using the tools.
@S3curityPlu5: Is your Developer License up-to-date?
@Kenan: We both have the Lenovo X1 Carbon Touch i5/4Gb RAM (a business model). You can also get an i7/8Gb model.
For consumers, the Lenovo Yoga is the equivalent model.
@s3curityConsult: Weird, if you run procdump -ma -i c:\dumps after the VS install, it should be set as the AeDebug Debugger. (Equally, if you run WinDbg -I it should be the debugger).
What values do you have in these locations?
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebugHKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\AeDebug
@Peter: I think the only place they are sold is the MS Company store on the Redmond campus. I don't think they are at the Retail Stores or Online...
@loverboy: No idea - they might have deleted it themselves. We wouldn't have culled that.
@loverboy: What do you mean? Did they get stripped in a post?
(Yes, codemachine has a great debugger extension)
@s3curityConsult: Not sure how to look in to this one.
Send an email to firstname.lastname@example.org and email@example.com.
Gov, Chad, Larry and myself will talk to you about it.
@Ben: To avoid ProcDumpExt executing .loadby sos mscorwks/clr & .cordll -l, after detecting the CLR present, make this environment variable and set it to 0.
setx PROCDUMPEXT_LOADCORDLL 0
In a version of ProcDumpExt I'm running (v7.7), it doesn't do the loading if SOS is already loaded. I'll look in to releasing it after I make sure all the new functionality isn't Microsoft Internal.