I have just had another unexpected crash using TH2 Demo in X2 today, which this time produced a minidump. My previous crashes (two days ago) were hanging type crashes. Before hanging completely I had partial control of some functions of Sonar in particlular the file system and I was able to do as save-as of my project, no minidumps produced.
 
I went to reported the crash today since I had a Sonar mindump, but find the report form does not have file attachments for minidumps. In past reports I was able to atttach minidumps. I thought minidumps helped the debugging process?.

As far as I'm aware the minidump is part of the report that is automatically sent to Cakewalk. I just clicked OK on mine to send it and I got an e-mail confirming that it had been sent and received with a reference number.

synkrotron


As far as I'm aware the minidump is part of the report that is automatically sent to Cakewalk. I just clicked OK on mine to send it and I got an e-mail confirming that it had been sent and received with a reference number.

 
 
I am not getting confirmation my error report is going through after finding how to add minidump.

Still not getting confirmation email that Reported Problem has been received and cannot go into report number. When I put in my new report number I get a report I submittted in May 2012.

Is Problem Reporting temporarily not working?.

It's working.


We should clarify the difference between the automated Fault Reporter system and the Problem Report Form.


If the Fault Reporter tool comes up in SONAR, then that means a .dmp file should be created behind the scenes. This typically won't come up if you experience a "hanging" type crash and no .dmp was ever created. When the Fault Reporter tool comes up, if you send the report anonymously, it will not email you a confirmation number. If you decide you want to be notified and enter your email address, then you'll get a confirmation email. I just tested this myself and it's indeed working.


The minidumps are sent automatically when you submit the report, you do not need to attach additional .dmp files manually after submitting.  What you're seeing on your end is just a status page, so it's normal to not see a reference of the file. They go into an internal debugging system that collects these details automatically.


The ability to add more files is not available on Fault Reports unless we need to ask for additional details because in most cases we already have enough details regarding the crash. One of the main reasons for this is because it's not useful to have multiple .dmp files tied to a singular CWBRN report. If we resolve one crash referenced in one .dmp file, but not another crash from the other .dmp file, updating the single report to "fixed" would make no sense. In other words, there really should be a separate report for each crash. If a dev does need more info, however, we'll open up the report for more info and comments and notify you via the email address you provided.


If you have a "hanging" type crash where you needed to generate a .dmp file manually, or if you just want to report a bug in general, this would be when you'd want to fill out the Problem Report Form manually (found here: http://www.cakewalk.com/support/contact/problemreport.aspx )


For "problem reports" (i.e. filling out the problem report form manually), you can add any files or additional messages as this does not go through the same automated system.


I hope that helps to clarify.

Ryan my music of is not on Internet. So when it crashed I took the mini dump file and tried to send along with report I found. Othing that allowed me to attach a file. This was using the problem reporter. 

Ryan Munnis [Cakewalk]

For "problem reports" (i.e. filling out the problem report form manually), you can add any files or additional messages as this does not go through the same automated system.


I hope that helps to clarify.

This is what I am trying to do but it does not seem to be working.
 
It creates "Problem Report Status" on the Cakewalk website, using the automatic file number CWBRN-xxxxx system.
 
When I add the minidump file to the report and "submit your file" the webpage changes.
 
Webpage says Your file has been sent. Click here to return to the report. On clicking here the webpage returns to a report I made in May 2012 and not the report I have just made.

(Side note: I pulled out your hyperlink as it contained your personal email)

I understand what you're referring to now. When that email was sent (the one you're pasting above), it was prior to your report being updated. At the time, it was a "New" report so any details could be added.

Your report was eventually updated to "Under Investigation" and then "Submitted to Development". These are human actions. Someone looked at the details of your report and determined that they had enough information to pass it along officially. I can see the entire history of it on my end. 

In truth, it was actually me on this report. I ran your .dmp file through our debugging symbols and added the crash info to the internal report with your details of what happened. This is essentially the same exact thing the Fault Reporter does, it just does it very quickly and doesn't require much human interaction (if any at all).

Your report currently set to "Status Changed" because it looks like it moved around internally a bit with some additional info. Messaging is closed for the report unless the devs or QA need more information. If that were to be the case, when they changed the report to "More Info Needed" it would open up some fields for you to add messages and files.

The point of the Problem Report system ultimately is for a user to report a problem and then for us to decipher what the problem is. Once we've determined whether or not its a bug or a SONAR related crash, we push it to our system internally and the report turns to a read-only report. When it gets resolved, the final stage emails the user so they are aware of the resolution. 

Allowing more information to continually be added only confuses things after that point. This particular form isn't meant to be a back and forth correspondence between the end user and our development team indefinitely. If we're closing out the report, it's not because we're trying to be rude, it's really us just trying to be more efficient.

It also allows us to not receive profane emails when customers disagree because they don't understand that things like "Closed - Feature Request" only means we pushed the information to a different team of Cakewalk employees (and yes... this happens a lot ;). 

I guess what I'm trying to get at is that it looks like your report was processed completely normally as intended by the system. You guys are all extremely helpful reporting this information to us, but you shouldn't have to worry yourselves about the day-to-day status changes with what we do internally. What I would worry about is:

1) Was the report clear? Check, yes it was.
2) Did Cakewalk acknowledge it? Check, yes they did.
3) Is it fixed yet? I'm not sure. I tried following your recipe but I'm unable to replicate it. Are you still running into this crash?

On the  pressing "View an Existing Report" in Problem reporter it comes up with my May 2012 report number and my email address.

If I put in a new report number (say 11155) or clear them both leaving the inputs  blank and press "Find Report". In the first case I get my May 2012 report and not my new report number. In the second case I get my May 2012 report and not an error message.
 
Whats happening?.
 
 

What's happening is there's a long-standing bug in the web page. Instead of taking the web page's input fields, it takes a cookie created by a previous report submission. Maybe find & delete the cookie or use a different browser, a different login, or a different computer.