C.3.5 Using ddd on Main and Proc Code
The GNU ddd symbolic debugger is (usually) built on top of the dde command line
debugger. Both tools are provided on all Linux systems.
1. To debug RVP9/Main code:
a. (Optional) Type b main to cause ddd to break on the first executable line after all
of the dynamic library references have been resolved.
This is a good way to get started, because you may break on any entry point within
RVP. Before the libraries are loaded, it is possible that ddd cannot
find all its
symbols.
b. Type:
$ cd /home/operator/src/rda/rvp9 main
$ make –j2
$ cd open
$ ddd rvp9main
The SITE and OPEN code is first compiled in the private development tree and then
the RVP executable that resides in the OPEN area runs.
c. To
redefine the environment variable OPTIMIZEFLAG=–g, remove the -O2 that is
normally there.
This causes the Makefiles to build non-optimized code, which generally behaves
more smoothly in a symbolic debugger.
d. Do one of the following:
• Type run in the ddd execution window
• Use run –nod to skip the powerup diagnostics and speed up your development
cycle.
Appendix C – RVP900 Developer Notes
379
To Next Page
Loading...