gdb is the GNU debugger. Although originally designed to operate with the GNU C compiler (gcc), gdb can be used to debug programs compiled from a variety of different compilers, including vendor-supplied C and Fortran compilers on several platforms (if compiled with debugger symbol information).
Emacs includes a GDB mode for simultaneously debugging and editing programs.
See Also:
ddd is a wrapper around the GDB, DBX, or XDB debuggers. In addition to the command-line interface of the dependent debugger, DDD provides a common graphical user interface to support debugging tasks. The DDD graphical data display allows for interactive exploration of data structures.
See Also:
dbx is the Berkeley UNIX symbolic debugger. It is available on Solaris and Digital Unix, and most useful with the vendor-provided compilers.
dbx can only be used on programs compiled with debugging information included (usually by compiling with the -g option). Core dumps can also be probed using dbx to determine the cause of the crash.
Dbx on different architectures may have slightly different features enabled or enhanced. Consult the appropriate dbx manual page on the for specifics.
Purify is designed to track down memory leaks and invalid memory use errors quickly and easily. Purify is installed in /s/purify on the Solaris Sparc workstations.
To use Purify with
g++ use:
purify -g++ -collector=/s/purify/collect2 followed by the
normal link options.For example, to link and purify foo with foo.o and bar.o:
purify -g++ -collector=/s/purify/collect2 gcc foo.o bar.o -o foo
See Also:
Purecov is a test coverage measurement tool. It is installed in /s/purecov on Solaris Sparc workstations.
See Also:
purelink is installed in /s/purelink on Solaris Sparc worstations.
See Also:
quanity is installed in /s/quantify on Solaris Sparc workstations.
See Also:
Sun Workshop is an integrated development environment available on all our Solaris workstations (X86 and SPARC, although Fortran 90 is not available on X86). A dbx-based debugger is part of the Workshop environment.
To use the Sun Workshop, you will need to run /usr/openwin/bin/ttsession first. Then run workshop
Note: OpenWindows and the Sun Workshop Integrated Development Environment are not supported by the Computer Systems Lab. The compilers included in Sun Workshop are supported.
See Also: