Debugging Desktop Client

docs
,
1

Debugging Desktop Client

When ASAP desktop client unexpectedly crashes.

Step-by-step guide

  1. On target computer install ASAP desktop client with debug enabled version (includes pdb filed with debug symbols).

  2. On target computer install DebugDiag utility (version 1.2 from http://www.microsoft.com/en-us/download/details.aspx?id=26798, choose version acoording machine architecture). Please, don’t try to install the newest version 2.0, because it is not stable and causes hangs.

  3. Start debug diag application
    7012353_176x52

  4. Start ASAP Desktop client (AsapArchitect.exe)

  5. In DebugDiag application in tab rules click on AddRule and select Crash
    7012355_464x408

  6. Click on Next and select “A specific process”
    7012356_202x48

  7. Click on Next and select AsapArchitect.exe as a Target process
    7012357_471x130

  8. Click on next and then in Advanced Configuration click on Breakpoints and add 3 non managed breakpuints
    7012359_408x40

  9. For Each breakpoint select MiniUserDump and keep Action limit set to 1
    7012360_480x453

  10. After Saving&Closing of advanced settings name the newly created rule (keep default settings)

  11. Activate the rule. The rule is active even if you close DebugDiag program.

  12. Close DebugDiag and ASAP Desktop Client.

  13. Now the system is ready for debugging and we can wait for unexpected crash.

Error rendering macro ‘contentbylabel’

parameters should not be empty