Reply to thread

Message

<blockquote data-quote="tourettes" data-source="post: 645628" data-attributes="member: 10858">This is not as bad as you make it sound <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /> It would be useful to use some already existing crash report framework to allow the application to send the crash data for some further analysis. Of course it shouldn't be used to generate any error reports, but instead of the analysed data it would show us the areas what components are causing the crashing etc. For example we could see that there is some really badly behaving directshow filter causing 25% of the application crashes. Or we could see that some of our own component has some speific code path that causes lot of trouble and we could review the code in that part. But in any case the data shouldn't be used directly for anything, especially for generating a Mantis report.</blockquote>

[QUOTE="tourettes, post: 645628, member: 10858"] This is not as bad as you make it sound :) It would be useful to use some already existing crash report framework to allow the application to send the crash data for some further analysis. Of course it shouldn't be used to generate any error reports, but instead of the analysed data it would show us the areas what components are causing the crashing etc. For example we could see that there is some really badly behaving directshow filter causing 25% of the application crashes. Or we could see that some of our own component has some speific code path that causes lot of trouble and we could review the code in that part. But in any case the data shouldn't be used directly for anything, especially for generating a Mantis report. [/QUOTE]

Verification