MantisBT - ParaView
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0009373ParaViewFeaturepublic2009-08-05 14:492016-08-12 09:57
ReporterDave DeMarle 
Assigned ToRobert Maynard 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionmoved 
PlatformOSOS Version
Product VersionDevelopment 
Target VersionSomedayFixed in Version 
Project
Topic Name
Type
Summary0009373: crash log analysis
DescriptionCan we give users option to send crash logs, containing scrubbed state or stack traces to Kitware? We can setup a receiver that will parse them, aggregate similar crashes together, and then show on cdash. This would make it easy to identify and fix the most serious flaws.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-08-05 14:49Dave DeMarleNew Issue
2011-02-04 14:22David PartykaAssigned To => Robert Maynard
2011-02-04 14:22David PartykaStatusbacklog => tabled
2011-02-04 14:23David PartykaTarget Version => Someday
2011-02-04 14:25David PartykaNote Added: 0025294
2011-06-16 13:10Zack GalbreathCategoryFeature Request => Feature
2016-07-21 14:07Cory QuammenStatusbacklog => expired
2016-08-12 09:57Kitware RobotNote Added: 0037679
2016-08-12 09:57Kitware RobotStatusexpired => closed
2016-08-12 09:57Kitware RobotResolutionopen => moved

Notes
(0025294)
David Partyka   
2011-02-04 14:25   
Brainstorming: Add try/catches to the ClientServer wrappings that would then report call stacks/statistics back to us.
(0037679)
Kitware Robot   
2016-08-12 09:57   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current ParaView Issues page linked in the banner at the top of this page.