1 /************************************************************************/
3 /* Instructions for Installing GDB
8 /* Copyright (C) 1987 Massachusetts Institute of Technology
10 /* =========================
12 /* NOTE: GDB is not currently a supported service of Project Athena
13 /* or of any other MIT organization. It is a set of programs which
14 /* I have written while working for Project Athena and which I
15 /* am making available to the MIT community in the hope that they
16 /* will prove useful. The decision as to whether GDB will become
17 /* supported is not mine to make. If you wish to express an opinion,
18 /* you should write a note including the following people on the
21 /* Prof. Steve Lerman (lerman@athena.mit.edu)
22 /* Prof. Jerry Saltzer (Saltzer@athena.mit.edu)
23 /* Dan Geer (geer@athena.mit.edu)
24 /* Noah Mendelsohn (noah@athena.mit.edu)
28 /* This file is named: README
30 /************************************************************************/
33 /************************************************************************/
37 /************************************************************************/
40 GDB is now available to the MIT community by anonymous ftp
41 from meathead.mit.edu. There are currently two files:
45 2) tar.file.Z (compressed tar.file containing all of gdb)
47 To install gdb, make a directory on your own system. It can
48 have any name, but we'll use gdb in this example:
52 % ftp meathead.mit.edu
53 ===>login as anonymous and give your user i.d. as passwd
56 ftp> bin <= make sure transfer of tar.file.Z
57 is done in binary mode, or the
58 uncompress step below may fail
62 % uncompress tar.file.Z <== this re-creates tar.file
63 If this step fails, you may have
64 forgotten to transfer the file
65 in binary mode (see above.)
66 % tar xf tar.file <== this extracts all the gdb
67 files from the tar file
69 /************************************************************************/
71 /* Making the gdb libraries
73 /************************************************************************/
75 To build the GDB library:
79 /************************************************************************/
81 /* Formatting documentation
83 /************************************************************************/
85 To format the gdb documents, you need scribe and access to a PostScript
86 printer. To make the user guide:
92 The reason you do it twice is that scribe requires two tries at a document
93 in order to get the forward references to page numbers right. The resulting
94 gdb_ugd.PS file may be sent to your PostScript printer:
98 To format the library reference manual:
104 /************************************************************************/
106 /* Writing and running programs
108 /************************************************************************/
110 The user guide tells you how to do this. Note that gdb.h winds up in
111 the gdb directory (where the tar.file is) when you use these installation
112 instructions, and so does libgdb.a. You will have to use the appropriate
113 Unix incantations, i.e. making links or telling cc and ld where to find
114 things in order for your compilations and loads to work. Make sure you
115 specify libgdb.a as one of the files to load along with your program.
117 /************************************************************************/
119 /* Building the database server
121 /************************************************************************/
123 The database server program is named dbserv. To build it:
127 This MUST be done on a machine where RTI Ingres is installed. You may
128 have to edit the makefile if /rtingres is not the directory where Ingres
129 lives, and you may have to put /rtingres/bin in your path before doing the
132 /************************************************************************/
136 /************************************************************************/
138 Various test programs are included in the tar.file. These are not intended
139 primarily for users, they are used for my private testing, but a few of
140 them are well commented and many of them work. The ones whose names begin
141 with the letter 't' are most likely to be useful. Each of them can be
144 /************************************************************************/
148 /************************************************************************/
150 Both the dbx and the Saber C debuggers have successfully executed many
151 GDB applications. I have found Saber to be particularly useful, and I
152 have included a .saberinit file which should serve as a starting point
153 for you. (Warning: .saberinit is supplied as a courtesy and I don't
154 guarantee to check it out with every re-release. If you know enough
155 to use Saber, you can probably make any minor corrections which may
156 be needed without too much trouble.) Note that both debuggers have trouble
157 on programs that fork. See the gdb_debug routine and the GDB_NOFORK flag
158 for a useful trick to avoid forking when debugging.
160 /************************************************************************/
164 /************************************************************************/
166 gdb-users@athena.mit.edu reaches all users of GDB bugs and fixes
168 gdb-news@athena.mit.edu announcements of interest to a wider
169 community of people who may not want to
170 know about every 2 line change to the system
172 noah@athena.mit.edu the author