From OpenSCADAWiki
Requirements for the error report
In order to exclude unnecessary overhead questions, or even premature closure of the error in the state "Not a bug", and to speed up the process of localization of the problem, it is recommended to follow the following requirements for the report:
- Specify the environment of the execution of OpenSCADA, that is: distribution and version of the operating system.
- Specify the version of OpenSCADA, including the SVN revision of the working branch.
- Specify the configuration and execution features.
In the case of free support, it is mandatory to reproduce the problem in standard configurations and in the demo database, especially when it is an emergency crash and it is not possible to generate a crash report or it is indescribable.
- Describe the actions that cause the error.
- Attach the OpenSCADA message protocol for a session with the error.
- Include report of the program crash — unroll the stack at the time of the crash.
- the report is usually generated automatically by generating it from the crashing process or pre-mortem memory dump (earlier) — just install GDB; refer to the next section for some specific here;
- to increase significantly the use of the stack unrolling, you must add debugging information, by setting the "-g" option during compilation, or install the ready debug package openscada-dbg;
- for problems, related to the blocking of one or more OpenSCADA threads, it may be useful to manually interrupt the program by call openscada-proj snapshot {ProjID} or the "SIGSEGV" signal, which will cause the formation of the fall-down report with the information about the hangover.