Developing tools

[jrv at vanzandt.mv.com (James R. Van Zandt)]

Massimo Morin <mmorin at schedsys.com> writes:
>The tools are the standard one:
...
>Debugging (this is my favorite)
>We use gdb 4.17. Personally I use DDD that is a graphical front end for
>gdb (xdb dbx etc...) and works great.
>On sun and Hp you can BUY purify for checking the memory leaks and the
>bad memory access but iti is expansive ($5k a machine).

I recommend electric fence.

>Debuggers 
>http://www.cs.colorado.edu/homes/zorn/public_html/MallocDebug.html

This web site mentions electric fence, but the description misses a
couple of important points: (1) it's free, and (2) It can debug a
dynamically linked executable without recompiling or even relinking -
just set an environment variable, so ld.so uses the electric fence
shared library for the memory functions instead of the regular ones
from libc.

		- Jim Van Zandt
-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).