.\" @(#)dbxrc.4 1.3 90/08/31 SMI; new for SunOS/SVR4
.TH DBXRC 4 "18 June 1998" " "
.SH NAME 
dbxrc, .dbxrc \- commands to dbx
.SH DESCRIPTION
The \f3.dbxrc\fP file
contains 
.B dbx
commands executed when you start
.B dbx.
It is used primarily for defining aliases and ksh functions, setting dbxenv variables, and defining GUI buttons. 
.LP
.B dbx
first searches for
.B .\|dbxrc
in the current working directory.
If
.B .\|dbxrc
does not exist in the current directory,
.B dbx
looks in the user's home directory. If no 
.B .\|dbxrc
file is found, the same search is made for the file
.B .\|dbxinit.
.LP
Use the
.B .\|dbxrc
file to configure
.B dbx.

.SH USAGE
.LP
See the 
.BR dbx (1)
man page for a description of
.B dbx
commands.
.SH EXAMPLES
.LP
Here is an example of a 
.B .\|dbxrc
file
that a
.SM FORTRAN
user of
.B dbx
might use:
.LP
.RS
.B "dbxenv stack_max_size 10"
.br
.B "dbxenv output_base 16
.br
.B "catch FPE"
.RE
.LP
The output of the 
.B dbx
command 
.B help dbxrc
can be used as an initial 
.B .\|dbxrc
file. For example:
.IP 
\f3help dbxrc\fP > \f3.\|dbxrc\fP
.LP
Many helpful ksh functions are documented in this
\f3help dbxrc\fP output.
.SH "SEE ALSO"
.BR dbx (1) ,
.BR workshop (1).
.SH NOTES
.LP
Users of earlier releases of
.B dbx
may have used their
.B .dbxrc
file to set breakpoints. The modules and Auto-Read facilities now cause 
.B dbx 
to read 
.B .dbxrc
.I before
the symbol table information rather than 
.IR after .
.LP
As a workaround, you can define an alias in your
.B .dbxrc
file which sources another file of 
.B 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, just call the alias immediately after you call
.B dbx .