Contact

If you have any comments or questions regarding the installation or use of the Scalasca Trace Tools, please get in touch with the development team:

We are happy to assist, however, please note that support can only be provided on a best-effort basis.

Reporting bugs

Like every other software, the Scalasca Trace Tools may contain bugs. If you encounter obviously broken, weird, or otherwise unexplainable behavior, please report it to the development team, preferrably via email (see above).

Before doing so, however, please check the Open issues and limitations whether the issue is already known. If not, make sure to include at least the following information in your bug report:

• The Scalasca Trace Tools version reported by ‘scalasca --version’.
• The Scalasca Trace Tools configuration reported by ‘scalasca --show-config’.
• The Score-P version reported by ‘scorep --version’.
• The Score-P configuration reported by ‘scorep-info config-summary’.
• The exact command line of the failing command.
• The exact failure/error message, which can usually be found in the job’s standard error output log and/or the scout.err file located in the experiment archive directory.

Also, if the trace analysis fails, please retain any generated core files and, if possible, try to generate a call stack of the failure using a debugger and include it in the report. In addition, archive a copy of the entire experiment archive directory including the event trace data, as this may be required to aid in debugging. However, ONLY PROVIDE TRACE DATA IF EXPLICITLY REQUESTED, as the data volume may be excessive.