共用方式為

The DebugDiag 2.0 Team

  • 發行項

Project Manager:

  • Mourad Lagdas

Lead Developer:

Core Team: 

  • Bret Bentzinger
  • Brian Roder
  • Ivanov Cepeda Pinto
  • Tomas Restrepo
  • Trevor Fellman
  • Richard Marr 

Script Conversion Team:

  • Amol Mehrotra
  • Devendra Asane
  • Nazeef Mallick
  • Puneet Gupta (Script Conversion Team Lead)
  • Rajkumar Rangaraj
  • Rakki Muthukumar
  • Santhosh Somayajulu
  • Shamik Misra
  • Sunil Kumar Chakrapani

Additional Contributors:

  • Dario Spilkin
  • George Archer
  • Jack Davis
  • Jeremy Phelps (Nasty Bug Ninja)
  • Kelvin Houghton
  • Larry Wall
  • Prakash Patel
  • Rodney Viana
  • Todd Foust

External Contributors:

  • Practices Checker: Sean Thompson
  • DynamicsAX: Tariq Bell, Pere Turegano, Erik Engstrom, Doug Bartley
  • CLRMD: Lee Culver

Comments

  • Anonymous
    November 20, 2013
    Thanks for looking and upgrading this very useful tool to new shape. Congrats Team!

  • Anonymous
    November 25, 2013
    Congrats Team!

  • Anonymous
    December 02, 2013
    this error is occurring, whereas the previous version did not occur: Probe of msdl.microsoft.com/.../file.ptr failed: The remote server returned an error: (407) Proxy Authentication Required. How set access ?

  • Anonymous
    December 02, 2013
    Hi, if I set path with this format : c:filespdbs1;c:filespdb2 path not parsed correctly

  • Anonymous
    December 02, 2013
    I'd like feature like this:

  • attach to service for exception capture;
  • after dump, restart service for running state

  • Anonymous
    December 02, 2013
    The analysis result show this error: Found file C:Softmscordacwks_X86_X86_2.0.50727.3649.dll but file timstamp:size 1366625120:1015808 != desired 1366613203:5939200, rejecting. What happened? the module is the same on dumps which have been generated.

  • Anonymous
    December 11, 2013
    @lSalamon the mscordacwks issue is a bug in clrmd and it's resolved in our next release.  We're targeting early 2014 for the update.

  • Anonymous
    December 11, 2013
    The comment has been removed

  • Anonymous
    January 08, 2014
    After installing and using "Debug Diagnostic Tool" to add rule and export the rule, how can we import the rule and activate the crash capture rules in unattended way to another 1000 machines by using scripts? Are there any scripting commands to do this? I could not find anywhere.

  • Anonymous
    January 08, 2014
    After installing Debug Diag 2.0 on a x64 machine, when attempting to diag a .Net 4.0 website on IIS (windows 2008 R2), the memory of the DbgSvc.exe grows without bounds.  This occurs when an exception is established for .Net CLR to take a stack trace.  This was not occurring on v1.2.  After uninstall 2.0 and re-installing 1.2, the problem is now occurring on v1.2 as well. Please advise!

  • Anonymous
    January 20, 2014
    @Wade Mascia: Thank you for fixing that bug!  I had the same issue with mscordacwks.dll not being found despite having the correct version with the correct name.  I cannot use Debug Diag 2.0 until it is resolved.  I had to downgrade to a prior version.

  • Anonymous
    January 29, 2014
    We are seeing the same unbound memory growth mentioned above by Bugged. Any suggestions?

  • Anonymous
    February 03, 2014
    The comment has been removed

  • Anonymous
    February 12, 2014
    Any update on the " issue with mscordacwks.dll not being found despite having the correct version with the correct name. " I've been creating analysis rules for defect triage but without the ability to support different dacs its a non-starter for us

  • Anonymous
    April 03, 2014
    Is there a C# example to produce the same CrashHangAnalysis report using the API?  

  • Anonymous
    May 26, 2014
    @Dave - We ship a ton of samples at <DebugDiagInstallDir>SamplesAnalysisRules, and you can always reflect out the code for <DebugDiagInstallDir>AnalysisRulesDebugDiag.AnalysisRules.dll @Gary/All - The fix is included in our latest update:  www.microsoft.com/.../details.aspx

  • Anonymous
    May 27, 2014
    Wade, thank you very much! My initial testing shows it to run like a champ. I'll be back with updates as time permits. Regards, Gary

  • Anonymous
    November 07, 2014
    The comment has been removed

  • Anonymous
    January 19, 2015
    Thank you the team for the great tools.

  • Anonymous
    March 12, 2015
    The comment has been removed

  • Anonymous
    April 28, 2015
    The comment has been removed

  • Anonymous
    July 07, 2015
    The comment has been removed

  • Anonymous
    July 10, 2015
    I am getting the same E_FAIL error on OpenDump as Alex is.  Any solution/workaround?

  • Anonymous
    November 30, 2015
    Same issue for me running DebugDiag 2.2.0.13 Getting the error when trying to analyze dumps

  • Anonymous
    December 21, 2015
    The comment has been removed

  • Anonymous
    January 13, 2016
    The comment has been removed

  • Anonymous
    January 31, 2016
    we are seeing application slowness when we activate Stack Overflow rule in Debug diagnostic Tool v 2.2, if we de-activate the rule application working fine we are not seeing any slowness, Can someone please share why we are seeing this slowness after activating this rule.