How Does The Debugging Option -g Change the Binary Executable?

by

-g tells the compiler to store symbol table information in the executable. Among other things, this includes:

  • symbol names
  • type info for symbols
  • files and line numbers where the symbols came from

Debuggers use this information to output meaningful names for symbols and to associate instructions with particular lines in the source.

For some compilers, supplying -g will disable certain optimizations. For example, icc sets the default optimization level to -O0 with -g unless you explicitly indicate -O[123]. Also, even if you do supply -O[123], optimizations that prevent stack tracing will still be disabled (e.g. stripping frame pointers from stack frames. This has only a minor effect on performance).

With some compilers, -g will disable optimizations that can confuse where symbols came from (instruction reordering, loop unrolling, inlining etc). If you want to debug with optimization, you can use -g3 with gcc to get around some of this. Extra debug info will be included about macros, expansions, and functions that may have been inlined. This can allow debuggers and performance tools to map optimized code to the original source, but it’s best effort. Some optimizations really mangle the code.

For more info, take a look at DWARF, the debugging format originally designed to go along with ELF (the binary format for Linux and other OS’s).

More Related Contents:

  1. How to generate gcc debug symbol outside the build target?
  2. Why do the addresses in my assembler dump differ from the addresses of registers?
  3. Why does the order in which libraries are linked sometimes cause errors in GCC?
  4. Change stack size for a C++ application in Linux during compilation with GNU compiler
  5. GCC dump preprocessor defines
  6. LD_LIBRARY_PATH vs LIBRARY_PATH
  7. CUDA incompatible with my gcc version
  8. How to install GCC piece by piece with GMP, MPFR, MPC, ELF, without shared libraries?
  9. How to see which flags -march=native will activate?
  10. How can I tell, with something like objdump, if an object file has been built with -fPIC?
  11. How to print every executed line in GDB automatically until a given breakpoint is reached?
  12. exit.c:(.text+0x18): undefined reference to `_exit’ when using arm-none-eabi-gcc
  13. How to cross compile from Mac OS X to Linux x86?
  14. What does the compiler error “missing binary operator before token” mean?
  15. Selectively remove a warning message using GCC
  16. How to Install gcc 5.3 with yum on CentOS 7.2?
  17. How to specify non-default shared-library path in GCC Linux? Getting “error while loading shared libraries” when running
  18. gcc/g++ option to place all object files into separate directory
  19. Cuda Clang and OS X Mavericks
  20. How to detect SSE/SSE2/AVX/AVX2/AVX-512/AVX-128-FMA/KCVI availability at compile-time?
  21. How is -march different from -mtune?
  22. How can I see parse tree, intermediate code, optimization code and assembly code during COMPILATION?
  23. How to set a variable in GCC with Intel syntax inline assembly?
  24. long double (GCC specific) and __float128
  25. How to write multiline inline assembly code in GCC C++?
  26. Errors that refer to a bunch of unresolved OpenSSL symbols that clearly exist?
  27. How to do bidirectional or reverse debugging of programs?
  28. clang (LLVM) inline assembly – multiple constraints with useless spills / reloads
  29. Hiding symbol names in library
  30. How to view C preprocessor output?

Leave a Comment