NAME

debugger − OpenWindows interface for the dbx source-level debugger

SYNOPSIS

debugger [ −I dir ] [ −kbd ] [ −Wfsdb/-fullscreen ] [ execfile [ corefile | processID ] ]

DESCRIPTION

debugger is a source-level debugger for ANSI C, C++, Pascal, and FORTRAN programs.  debugger is a standard tool that runs within the OpenWindows environment (Version 3.0 and later).  It accepts the same commands as dbx, but provides a convenient, graphical user interface. 

You can use the mouse to set breakpoints, examine the values of variables, control execution, browse source files, and so on.  debugger has separate panes for viewing source code, entering commands, monitoring expressions, setting properties and other uses. 

execfile is an executable file produced by any other Sun compiler (or a combination of them) with the −g flag specified to produce symbol information in the executable file.  IMPORTANT: every stage of the compilation process, including the linking phase, must include the −g option.  If no execfile is specified, you can use the debug command to specify the program to be debugged.  The executable file contains a symbol table which includes the names of all the source files translated by the compiler to create it.  These files are available for perusal while you are using the debugger. 

If a file named core exists in the current directory or a corefile is specified, debugger can be used to examine the state of the program when it faulted. 

Giving a processID instead of a corefile halts that running process and allows you to start debugging that program.  Detaching the debugger from the process allows that process to continue to execute. 

debugger executes commands in file .dbxinit file immediately before it reads the symbol table.  debugger first searches for .dbxinit in the current directory.  If .dbxinit does not exist in the current directory, debugger looks in the user’s home directory. 

The Collector is a pop-up window in debugger that is a graphical user interface tool for collecting performance data on a target application.  The data is contained in buckets called samples.  A collection of samples is called an experiment.  The collected performance data can be viewed in the displays of the Analyzer , which is a graphical data analysis tool.  See Performance Tuning an Application for details on using the Collector and the Analyzer tools. 

OPTIONS

−I dir Add directory to the list of directories that are searched when looking for a source file.  Normally debugger looks for source files in the current directory and then in the directory where execfile is located.  The directory search path can also be set with the use command.  Multiple −I options may be given. 

−kbd Debugs a program that sets the keyboard into up/down translation mode.  This flag is necessary if you are debugging a program that uses up/down encoding. 

−Wfsdb/-fullscreen
OpenWindows only. Debug program on the same server on which you are displaying it. Active grabs are disabled when you press a key, move the pointer, or perform a server action. Passive grabs are disabled when you press a mouse button.

USAGE

Refer to dbx(1) for a summary of dbx commands, or to Debugging a Program for more complete information on using debugger . 

Refer to dbx(1) for a summary of Collector commands, or Performance Tuning an Application for more complete information on using the Collector. 

FILES

core default core file

.dbxinit local dbx initialization file

/.dbxinit user’s dbx initialization file

SEE ALSO

dbx(1), dbxinit(5)

Debugging a Program . 

  —  Last change: 20 August 1992