Skip to content

FAQs.md

Latest commit

 

History

History
45 lines (28 loc) · 2.2 KB

FAQs.md

File metadata and controls

45 lines (28 loc) · 2.2 KB

FAQs

Table of Contents

Debugging Setup

The debugger needs to be configured to know which executable and debugger to use:

Click menu item: Debug -> Add Configuration...

The file launch.json will now be open for editing with a new configuration. The default settings will probably work except that you need to specify the program setting.

See the Documentation/Debugger folder in this repository for more in-depth documentation on how to configure the debugger.

Why is debugging not working?

My breakpoints aren't being hit

When you start debugging, if it is showing that your breakpoints aren't bound (solid red circle) or they are not being hit, you may need to enable debug symbols during compilation.

Debugging starts but all the lines in my stack trace are grey

If your debugger is showing a grey stacktrace or won't stop at a breakpoint,or the symbols in the call stack are grey then your executable was compiled without debug symbols.

How to enable debug symbols?

Enabling debug symbols are dependent on the type of compiler you are using. Below are some of the compilers and the compiler options necessary to enable debug symbols.

When in doubt, please check your compiler's documentation for the options necessary to include debug symbols in the output. This may be some variant of -g or --debug.

  • Clang (C++)

    • If you invoke the compiler manually then add the --debug option.
    • If you're using a script then make sure the CXXFLAGS environment variable is set; e.g. export CXXFLAGS="${CXXFLAGS} --debug"
    • If you're using CMake then set make sure the CMAKE_CXX_FLAGS is set; e.g. export CMAKE_CXX_FLAGS=${CXXFLAGS}

  • Clang (C)

    See Clang C++ but use CFLAGS instead of CXXFLAGS.

  • gcc or g++

    If you invoke the compiler manually, add the -g option.

  • cl.exe

    Symbols are located in the *.pdb file.