When using GDB to debug a C + + program, it feels like you are not doing the process and jumping around

When debugging with GDB, it relies on the compilation result of g++, because the optimization is used by default at compile time, so it does not execute in code order, but only needs to turn off the g++ compilation optimization.

GDB Debug program when the print variable value will appear <value optimized out> situation, can be in the GCC compile time with the-o0 parameter, meaning is not compiled optimization, debugging will be smooth, the running process will not jump to jump, When publishing a project remember not to use the-o0 parameter item, gcc default compilation or add-o2 optimized compilation will increase the speed of the program.

When using GDB to debug a C + + program, it feels like you are not doing the process and jumping around