gdb/README

   1 This is GDB, a source-level debugger intended for GNU,
   2 presently running under un*x.
   3
   4 Before compiling GDB, you must set up links to five files according to
   5 the kind of machine you are running on.  To do this, type `config.gdb
   6 machine', where machine is something like `vax' or `sun2'.  This
   7 creates links named `param.h', `opcode.h', `pinsn.c', and `infdep.c'.
   8
   9 Once these files are set up, just `make' will do everything,
  10 producing an executable `gdb' in this directory.
  11
  12 About the machine-dependent files...
  13
  14 m-<machine>.h
  15
  16 This file contains macro definitions that express information
  17 about the machine's registers, stack frame format and instructions.
  18
  19 <machine>-opcode.h, <machine>-pinsn.c
  20 These files contain the information necessary to print instructions
  21 for your cpu type.
  22
  23 <machine>-dep.c
  24 Those routines which provide a low level interface to ptrace and which
  25 tend to be machine-dependent.  (The machine-independent routines are in
  26 `infrun.c' and `inflow.c')
  27
  28 About debugging gdb with itself...
  29
  30 You probably want to do a "make TAGS" after you configure your
  31 distribution; this will put the machine dependent routines for your
  32 local machine where they will be accessed first by a M-period .
  33
  34 Also, you want to make sure that gdb is not compiled with shared
  35 libraries on the Sun 4.  And you want to make sure that you've
  36 compiled gdb with your local cc or taken appropriate precautions
  37 regarding ansification of include files.  See the Makefile for more
  38 information.
  39
  40 The "info" command, when executed without a subcommand in a gdb being
  41 debugged by gdb, will pop you back up to the top level gdb.  See
  42 .gdbinit for more details.
  43
  44 About languages other than C...
  45
  46 C++ support has been integrated into gdb; it works, but somewhat
  47 buggily.  Pascal support has not yet been integrated in gdb; the work
  48 is being done.
  49
  50 About reporting bugs...
  51
  52 The correct address for reporting bugs found with gdb is
  53 "bug-gdb@prep.ai.mit.edu".  Please send all bugs to that address.
  54
  55 About xgdb...
  56
  57 xgdb.c was provided to us by the user community; it is not an integral
  58 part of the gdb distribution.  The problem of providing visual
  59 debugging support on top of gdb is peripheral to the GNU project and
  60 (at least right now) we can't afford to put time into it.  So while we
  61 will be happy to incorporate user fixes to xgdb.c, we do not guarantee
  62 that it will work and we will not fix bugs reported in it.
  63
  64 For those intersted in auto display of source and the availability of
  65 an editor while debugging I suggest trying gdb-mode in gnu-emacs.
  66 Comments on this mode are welcome.
  67