- matching the program being executed should be present. Note that if you use
- Microsoft Visual C++ compiler, you can create PDB files even for the programs
- built in release mode and it doesn't affect the program size (at least if you
- don't forget to add @c /opt:ref option which is suppressed by using
- @c /debug linker option by default but should be always enabled for
- release builds). Under Unix, you need to compile your program with debugging
- information (usually using @c -g compiler and linker options) to get the
- file and line numbers information, however function names should be available
- even without it. Of course, all this is only @true if you build using a recent
- enough version of GNU libc which provides the @c backtrace() function
- needed to walk the stack.
-
- @ref overview_debuggingoverview "debugging overview" for how to make it
- available.
+ matching the program being executed should be present.
+ Note that if you use Microsoft Visual C++ compiler, you can create PDB files
+ even for the programs built in release mode and it doesn't affect the program
+ size (at least if you don't forget to add @c /opt:ref option which is suppressed
+ by using @c /debug linker option by default but should be always enabled for
+ release builds).
+ Under Unix, you need to compile your program with debugging information
+ (usually using @c -g compiler and linker options) to get the file and line
+ numbers information, however function names should be available even without it.
+ Of course, all this is only @true if you build using a recent enough version
+ of GNU libc which provides the @c backtrace() function needed to walk the stack.
+
+ See @ref overview_debugging for how to make it available.