Intel® VTune™ Amplifier 2018 Help

Debug Information for Linux* Application Binaries

Compile your code using the -g option that usually produces debugging information in the DWARF format. If DWARF is not a default debugging information format for the compiler, use the -gdwarf-version option, for example: -gdwarf-2 or -gdwarf-3.

To enable generating the debug information with MinGW/Cygwin GCC* compilers:

Use -g option or -gdwarf-version (for example: -gdwarf-2, -gdwarf-3) if DWARF is not a default debugging information format.

Note

Intel® VTune™ Amplifier supports two ways of specifying a separate debug info file for an ELF executable/library binary:

Please refer to the Binutils documentation for more details on how to create separate debug info files and link them with an executable/library via debug link or build ID.

If your system and application modules have debug information, the VTune Amplifier is able to provide full-scale statistics on call stacks, source data, and so on. For example, you may use the Call Stack Mode on the filter toolbar to select the User/system functions option and view data on both user and system functions.

If the VTune Amplifier does not find debug information for the binaries, it statically identifies function boundaries and assigns hotspot addresses to generated pseudo names func@address for such functions, for example:

If a module is not found or the name of a function cannot be resolved, the VTune Amplifier displays module identifiers within square brackets, for example: [vmlinux].

If the debug information is absent, the VTune Amplifier may not unwind the call stack and display it correctly in the Call Stack pane. Additionally in some cases, it can take significantly more time to finalize the results for modules that do not have debug information.

See Also