NAME

dbxinit, .dbxinit − commands to dbx

DESCRIPTION

The .dbxinit file contains dbx commands that are executed when you start dbx or debugger.  For example, you might include the menu command to define menu items not otherwise displayed in debugger.  Or, you may include the toolenv command to set the attributes of the debugger window environment. 

dbx and debugger first search for .dbxinit in the current working directory.  If .dbxinit does not exist in the current directory, dbx and debugger look in the user’s home directory. 

Use the .dbxinit file to configure dbx and debugger.  Do not use .dbxinit to run commands that depend on the program having started execution, such as call, run, and step. 

USAGE

COMMANDS

See the dbx(1) man page for a description of dbx commands. 

EXAMPLES

Here is an example of a .dbxinit file that a FORTRAN user of dbx and debugger might use:

dbxenv case insensitive
button ignore edit
toolenv srclines 35
catch FPE

The first line of the file allows you to select upper- or lower-case variable names for displaying.  The second line sets up a button for the edit command.  The third line increases the size of the source window.  The fourth line turns on the catching of Floating Point Errors. 

SEE ALSO

dbx(1), debugger(1)

Debugging A Program

NOTES

Users of earlier releases of dbx may have grown used to setting breakpoints in their .dbxinit file. This does not work in this and the previous release of dbx because the modules and the Auto-Read facilities cause dbx to read .dbxinit before the symbol table information rather than after, as in earlier versions.

To work around this difficulty, you may define an alias in your .dbxinit file which will source another file of dbx commands; you can then set up this additional file to contain the breakpoint-setting commands.  Once you have set up this second file with the breakpoint commands, all you need do is call the alias immediately after you call dbx. 

The last line in .dbxinit may look something like this:

alias moredbx "source .dbxinit2"

The contents of .dbxinit2 may look something like this :

stop in main
stop in initial

Call dbx with the name of the program to be debugged.  Then, enter moredbx as the first command. 

  —  Last change: 20 August 1992