Scribd
Upload
83 views8 pages

How To Use Microsoft DebugDiag Tool

Uploaded by

V
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
83 views8 pages

How To Use Microsoft DebugDiag Tool

Uploaded by

V
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 8

DOWNLOAD PURCHASE BLOG FORUM SUPPORT ACCOUNT

Special offer for Brainspawn Forte users to cross grade to Cantabile Performer. Read More

Using Microsoft's Debug Diagnostics Tool

Sometimes (rarely) Cantabile or a plugin will crash in a way that the built-in crash
reporter can't handle. In these cases you can use the Microsoft Debug Diagnostics
tool to capture a crash report that we can use to diagnose the problem.

The follow steps describe how to use this tool.

1. Download the Debug Diagnostics tool from Microsoft. Note that there are two
versions available - one for x86 and one for x64. Be sure to download the one
that matches the platform you're running.

2. Install the Debug Diagnostics tool, accepting the default installation options.

3. Run the DebugDiag 2 Collection program which can now be found in your start
menu. (Hint: press the Windows start menu button and type "Debug" to find it
quickly)
4. Follow the DebugDiag wizard as follows. Set the Rule Type to Crash, and click
next
5. Set the Target Type as "A specific process":
6. On the next screen, ignore the list of processes and simply type "Cantabile.exe"
(without the quotes) into the Selected Process field and leave "This process
instance only" turned off, as shown below:

7. The rest of the wizard steps you can simply click Next:
8. You may be prompted about a "Symbol Search Path for Debugging". If so, click
Yes.
9. By the time you're finished it should look like this:

10. The DebugDiag tool it now configured to capture any unhandled exceptions in
Cantabile. If you can start Cantabile you should now disable Cantabile's built-in
crash reporting by going to Options -> Diagnostics and turning off "Generate
Crash dumps". If you can't start Cantabile, ignore this step.

11. Reproduce the crash in Cantabile if you can. If the crash is random or occassional
you can close the DebugDiag tool (the debug service will continue to run in the
background) and continue using Cantabile until the problem occurs.

12. Once the problem has occurred, start File Explorer (press Windows+E) and
navigate to the following folder:
C:\Program Files\DebugDiag\Logs\Crash rule for all instances of Cantabil

or if you're running on x86 platform:

C:\Program Files (x86)\DebugDiag\Logs\Crash rule for all instances of Ca

(you can check which path to use by starting DebugDiag tool again and looking in
the last column)

13. In that folder you should find the files similar to the following:

14. The files here will typically be too large to email. Instead zip them up and upload
them here and drop us an email describing the problem.

Once you've captured the crash report:

1. Disable the DebugDiag tools by starting it as shown in step 3 above.

2. Right click on the rule and choose "Deactivate Rule".

3. Go back into Cantabile -> Options -> Diagnostics and turn on "Generate Crash
Dumps" to re-enable Cantabile's built-in crash reporting.

support | about | contact | twitter | medium


Cantabile is designed and developed by Topten Software.
Copyright © 2019. All Rights Reserved.

You might also like