15. Submitting a bug report

Whenever encountering that Extrae fails while instrumenting an application or generating a trace-file, you may consider to submit a bug report to tools@bsc.es.

Before submitting a bug report, consider looking at the Frequently Asked Questions in appendix Frequently Asked Questions because it may contain valuable information to address the failure you observe.

In any case, if you find that Extrae fails and you want to submit a bug report, please collect as much as information possible to ease the bug-hunting process.

The information required depen whether the bug refers to a compilation or an execution issue.

15.1. Reporting a compilation issue

The following list of items are valuable when reporting a compilation problem:

  • Extrae version (this information appears in the first messages of the execution).
  • Extrae configuration information, such as:
    • the configure output and the generated config.log file.
    • versions of any additional libraries (PAPI, libunwind, DynInst, CUDA, OpenCL, libxml2, libdwarf, libelf, …)
  • The compilation error itself as reported by invoking make V=1.

15.2. Reporting an execution issue

The following list of items are valuable when reporting an execution problem:

  • Extrae version (this information appears in the first messages of the execution).
  • Extrae configuration information, such as:
    • the configure output and the generated config.log file,
    • versions of any additional libraries (PAPI, libunwind, DynInst, CUDA, OpenCL, libxml2, libdwarf, libelf, …), and/or
    • the ${EXTRAE_HOME}/etc/configured.sh output.
  • The result of the make check command after the Extrae compilation process.
  • Does the application successfully executes with and without Extrae?
  • Any valuable information from the system (type of processor, network, …).
  • Which type of parallel programming paradigm does the application use: MPI, OpenMP, OmpSs, pthreads, …, hybrid?
  • How do you execute the application? Which instrumentation library do you use?
  • The Extrae configuration file used.
  • Any output generated by the application execution (in either the output or error channels).
  • If the execution generates a core dump, a backtrace of the dump using the where command of the gdb debugger.