Debugger $($gdb$)$

Goals

How to write more efficient code

Where to look when hard$-$to$-$find bugs arise.

Note: You may use the supplied crash.cpp in any Linux environment $($compile using $-$g switch$)$ to experiment with all the commands that are available in gdb$,$ alternatively, you may use your own sample code to experiment and should use NetBeans$19$ or higher built$-$in gdb debugger. Here are the operations you should try:

Try setting and removing breakpoints

Step line$-$by$-$line in a method $($may be the main$))$ and observe changes in a variable

Try navigating the stack frames in the debugger $($observe how the call stack looks$)$

Finally, make a screenshot of your whole NetBeans window showing:

a$.$ The current line of code

b$.$ The stack trace tab

c$.$ The variables $ta{b}_{{?}_{?}}$