Debugging programs with DDD - simple tip
When using DDD to debug C/C++ programs, it is better to start DDD from an xterm in the same directory as the sourcecode/makefile/executable binary are in.
robert@debian:~/projects/cplusplus/_834v5010generator/src$ ddd &
When starting DDD from a GUI menu, I had to waste time navigating to the directory of interest. With launching from an xterm in the same directory as the stuff to debug, DDD defaults to that directory, making getting each DDD debugging session that much faster to get going on.
EDIT 2014-09-28
When a breakpoint is set in a loop, use the DDD command "Cont" to tell DDD to execute the program, but to again stop at the breakpoint.
EDIT 2014-11-02
When in a method or function, to get a variable to go into the DDD display, just double-click it. Useful to see how state of variables change, when stepping through a program.
While stepping through a program, if you put the cursor over a variable, a pop-up will display the variable's value.
2014-11-21
The DDD online manual is at https://www.gnu.org/software/ddd/manual/html_mono/ddd.html
2014-11-22
DDD Conditional Breakpoints
To create a conditional breakpoint: 1st just create a breakpoint. Once it exists in DDD, if you double-click that breakpoint, a pop-up will appear, and conditional statements can be added.
2015-01-25
Program, Run Again
Embarrassing, but true. Each debugging session, once the program had died or ended, I would close and restart DDD.
Just recently realized, instead just do: "Program, Run Again".
2016-09-05
Use the F2 key for testing a command-line program, so you can put in any needed command-line arguments.