Return to README CVS log

Up to [GNU Debugger] / gdb

Annotation of gdb/README, revision 1.1.1.2

1.1       root        1: This is GDB, a source-level debugger intended for GNU,
                      2: presently running under un*x.
                      3: 
1.1.1.2 ! root        4: Before compiling GDB, you must set up links to four 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', `m-init.h', `opcode.h', and `pinsn.c'.
        !             8: (Note: we lack information on certain machines.)
        !             9: 
        !            10: Also, `Makefile' must be changed to say `OBSTACK = obstack.o' instead
        !            11: of `OBSTACK=-lobstack' (unless you want to install obstack.o as
        !            12: /lib/libobstack.a).
        !            13: 
        !            14: Once these files are set up, just `make' will do everything,
        !            15: producing an executable `gdb' in this directory.
        !            16: 
        !            17: About the machine-dependent files...
        !            18: 
        !            19: m-<machine>.h
1.1       root       20: 
                     21: This file contains macro definitions that express information
                     22: about the machine's registers, stack frame format and instructions.
                     23: 
1.1.1.2 ! root       24: m-<machine>init.h
        !            25: 
1.1       root       26: This file defines one macro, which says how to round up from the
                     27: address of the end of the text of one .o file to the beginning of
                     28: the text of the next .o file.
                     29: 
1.1.1.2 ! root       30: <machine>-opcode.h, <machine>-pinsn.c
        !            31: These files contain the information necessary to print instructions
        !            32: for your cpu type.

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.