Reply to thread

Message

<blockquote data-quote="krntea" data-source="post: 161463" data-attributes="member: 28550">Certainly, when I get back from the office.&nbsp; Perhaps if this information is useful to the MP developers it should be required as part of the forum bug submisison process and might be beneficial to mentioned so in the office forum bug submission guidelines?Also, as you have also experienced the problems you could visit that time period in your own event logs to see how helpful they will be to this problem.I suspect my first post linking the first blog discussing the topic in the other thread might have be misleading, my apologies. You do not need people to analyse reports. You need a debugger, and a developer. If the Developer has the desire to know what line of code the crash/hang is on, they load the dump information into the debugger with a click, navigate to the source code line in a few seconds, and then start debugging as normal. All variables and their contents all along the call stack are at the developers disposition.&nbsp; If the code where the crash occurred looks Ok then try-catch info can be placed around the offending point and the user asked to run it, OR the developer can look at machine state info to see if something might be affecting the offending source, but usually it is quicker not to bother.No. The benefits of auto bug submission are so popular and widespread that there is code to do it out there already. Take the time to try out the codeproject crashrpt as I suggested in the linked thread - it is easy to integrate and will show you quickly what I am talking about.&nbsp; And as mentioned, you will find all high volume open source projects with many users have to use such systems already (Mozilla suite, Azeurus etc) due to the problems with forums I have already mentioned.Thanks,Keith.</blockquote>

[QUOTE="krntea, post: 161463, member: 28550"] Certainly, when I get back from the office. Perhaps if this information is useful to the MP developers it should be required as part of the forum bug submisison process and might be beneficial to mentioned so in the office forum bug submission guidelines? Also, as you have also experienced the problems you could visit that time period in your own event logs to see how helpful they will be to this problem. I suspect my first post linking the first blog discussing the topic in the other thread might have be misleading, my apologies. You do not need people to analyse reports. You need a debugger, and a developer. If the Developer has the desire to know what line of code the crash/hang is on, they load the dump information into the debugger with a click, navigate to the source code line in a few seconds, and then start debugging as normal. All variables and their contents all along the call stack are at the developers disposition. If the code where the crash occurred looks Ok then try-catch info can be placed around the offending point and the user asked to run it, OR the developer can look at machine state info to see if something might be affecting the offending source, but usually it is quicker not to bother. No. The benefits of auto bug submission are so popular and widespread that there is code to do it out there already. Take the time to try out the codeproject crashrpt as I suggested in the linked thread - it is easy to integrate and will show you quickly what I am talking about. And as mentioned, you will find all high volume open source projects with many users have to use such systems already (Mozilla suite, Azeurus etc) due to the problems with forums I have already mentioned. Thanks, Keith. [/QUOTE]

Verification