Skip to content

Adds a mean to autosart Python trace and to dump it in case of crash

guillaume Peillex requested to merge guillaume.peillex/paraview:enable_trace_autostart_2 into master

Themys users have stated out that when then are facing a bug that led to a crash, they have strong difficulties to reproduce this crash. Thus it prevent them to open a issue. This is problematic for the development team because it is not aware of the bug.

Those difficulties to reproduce the bug may be due to the bug itself. It can sometimes occurs randomly, but most of the time the user difficulty is that he does not remember all the set of actions that led to a crash.

Of courses he can save a state file but this file, as his name stands for, reflects the state of ParaView right before the crash. It does not contain all the history of user actions and it is not very useful for debugging sessions.

This MR proposes two things:

  • Add a setting that, when true, launches the python trace at ParaView's startup (this setting is false by default);
  • When a crash occurs, if a trace is started then dumps its content instead of an empty state as it is currently the case. Warns the user that a trace is dumped instead of a state.

For now, the setting is read in ParaViewMainWindow.cxx but it is maybe not the right place to do it because i obtain the following message:

warning: In /home/peillexg/paraview/Qt/Components/pqPropertyWidgetDecorator.cxx, line 61
warning: Cannot create decorator of type  "InputDataTypeDecorator"

I did not add a test yet.

Merge request reports