* README: Remove note about gcc warnings on alpha, these should be

	gone now.
	* c-exp.y, ch-exp.y, core.c, corelow.c, eval.c, fork-child.c,
	m2-exp.y, minsyms.c, nlmread.c, parse.c, putenv.c, regex.c
	remote-utils.c, stabsread.c:  Include <string.h>.
	* regex.c:  Include "defs.h", change re_comp argument to const char *.
	* infptrace.c (fetch_register, store_inferior_registers):  Change
	regaddr to type CORE_ADDR.
	* config/alpha/alpha-nw.mt, config/alpha/alpha-osf1.mt (MT_CFLAGS):
	Remove, no longer necessary now that we use bfd_vma for a CORE_ADDR.

1 files changed, 52 insertions, 53 deletions

diff --git a/gdb/README b/gdb/README
index d4834e24..b61a992 100644
--- a/gdb/README
+++ b/gdb/README
@@ -1,5 +1,5 @@
-		      README for gdb-4.9 release
-		    Updated 10-May-93 by Fred Fish
+		      README for gdb-4.12 release
+		    Updated 3-Feb-94 by Fred Fish
 
 This is GDB, the GNU source-level debugger, presently running under un*x.
 A summary of new features is in the file `NEWS'.
@@ -11,7 +11,7 @@ Unpacking and Installation -- quick overview
 In this release, the GDB debugger sources, the generic GNU include
 files, the BFD ("binary file description") library, the readline
 library, and other libraries all have directories of their own
-underneath the gdb-4.9 directory.  The idea is that a variety of GNU
+underneath the gdb-4.12 directory.  The idea is that a variety of GNU
 tools can share a common copy of these things.  Be aware of variation
 over time--for example don't try to build gdb with a copy of bfd from
 a release other than the gdb release (such as a binutils or gas
@@ -20,8 +20,8 @@ Configuration scripts and makefiles exist to cruise up and down this
 directory tree and automatically build all the pieces in the right
 order.
 
-When you unpack the gdb-4.9.tar.z or gdb-4.9.tar.Z file, you'll find
-a directory called `gdb-4.9', which contains:
+When you unpack the gdb-4.12.tar.gz file, you'll find a directory
+called `gdb-4.12', which contains:
 
   Makefile.in      config.sub*      glob/            opcodes/
   README           configure*       include/         readline/
@@ -31,7 +31,7 @@ a directory called `gdb-4.9', which contains:
 
 To build GDB, you can just do:
 
-	cd gdb-4.9
+	cd gdb-4.12
 	./configure
 	make
 	cp gdb/gdb /usr/local/bin/gdb	(or wherever you want)
@@ -52,7 +52,7 @@ More Documentation
 
    The GDB 4 release includes an already-formatted reference card,
 ready for printing with PostScript or GhostScript, in the `gdb'
-subdirectory of the main source directory.  (In `gdb-4.9/gdb/refcard.ps'.)
+subdirectory of the main source directory.  (In `gdb-4.12/gdb/refcard.ps'.)
 If you can use PostScript or GhostScript with your printer, you can
 print the reference card immediately with `refcard.ps'.
 
@@ -86,7 +86,7 @@ distribution.
 Info formatting programs, such as `texinfo-format-buffer' or `makeinfo'.
 
    If you have `makeinfo' installed, and are in the top level GDB
-source directory (`gdb-4.9', in the case of version 4.9), you can make
+source directory (`gdb-4.12', in the case of version 4.12), you can make
 the Info file by typing:
 
      cd gdb
@@ -112,7 +112,7 @@ format.  On its own, TeX cannot read, much less typeset a Texinfo file.
 
    If you have TeX and a DVI printer program installed, you can typeset
 and print this manual.  First switch to the the `gdb' subdirectory of
-the main source directory (for example, to `gdb-4.9/gdb') and then type:
+the main source directory (for example, to `gdb-4.12/gdb') and then type:
 
      make gdb.dvi
 
@@ -128,42 +128,42 @@ preparing GDB for installation; you can then use `make' to build the
 a single directory, whose name is usually composed by appending the
 version number to `gdb'.
 
-   For example, the GDB version 4.9 distribution is in the `gdb-4.9'
+   For example, the GDB version 4.12 distribution is in the `gdb-4.12'
 directory.  That directory contains:
 
-`gdb-4.9/configure (and supporting files)'
+`gdb-4.12/configure (and supporting files)'
      script for configuring GDB and all its supporting libraries.
 
-`gdb-4.9/gdb'
+`gdb-4.12/gdb'
      the source specific to GDB itself
 
-`gdb-4.9/bfd'
+`gdb-4.12/bfd'
      source for the Binary File Descriptor library
 
-`gdb-4.9/include'
+`gdb-4.12/include'
      GNU include files
 
-`gdb-4.9/libiberty'
+`gdb-4.12/libiberty'
      source for the `-liberty' free software library
 
-`gdb-4.9/opcodes'
+`gdb-4.12/opcodes'
      source for the library of opcode tables and disassemblers
 
-`gdb-4.9/readline'
+`gdb-4.12/readline'
      source for the GNU command-line interface
 
-`gdb-4.9/glob'
+`gdb-4.12/glob'
      source for the GNU filename pattern-matching subroutine
 
-`gdb-4.9/mmalloc'
+`gdb-4.12/mmalloc'
      source for the GNU memory-mapped malloc package
 
-'gdb-4.9/sim'
+'gdb-4.12/sim'
      source for some simulators (z8000, H8/300, H8/500, etc)
 
    The simplest way to configure and build GDB is to run `configure'
 from the `gdb-VERSION-NUMBER' source directory, which in this example
-is the `gdb-4.9' directory.
+is the `gdb-4.12' directory.
 
    First switch to the `gdb-VERSION-NUMBER' source directory if you are
 not already in it; then run `configure'.  Pass the identifier for the
@@ -171,7 +171,7 @@ platform on which GDB will run as an argument.
 
    For example:
 
-     cd gdb-4.9
+     cd gdb-4.12
      ./configure HOST
      make
 
@@ -190,8 +190,8 @@ you may need to run `sh' on it explicitly:
      sh configure HOST
 
    If you run `configure' from a directory that contains source
-directories for multiple libraries or programs, such as the `gdb-4.9'
-source directory for version 4.9, `configure' creates configuration
+directories for multiple libraries or programs, such as the `gdb-4.12'
+source directory for version 4.12, `configure' creates configuration
 files for every directory level underneath (unless you tell it not to,
 with the `--norecursion' option).
 
@@ -199,10 +199,10 @@ with the `--norecursion' option).
 directories in the GDB distribution, if you only want to configure that
 subdirectory; but be sure to specify a path to it.
 
-   For example, with version 4.9, type the following to configure only
+   For example, with version 4.12, type the following to configure only
 the `bfd' subdirectory:
 
-     cd gdb-4.9/bfd
+     cd gdb-4.12/bfd
      ../configure HOST
 
    You can install `gdb' anywhere; it has no hardwired paths. However,
@@ -231,13 +231,13 @@ directory.  If the path to `configure' would be the same as the
 argument to `--srcdir', you can leave out the `--srcdir' option; it
 will be assumed.)
 
-   For example, with version 4.9, you can build GDB in a separate
+   For example, with version 4.12, you can build GDB in a separate
 directory for a Sun 4 like this:
 
-     cd gdb-4.9
+     cd gdb-4.12
      mkdir ../gdb-sun4
      cd ../gdb-sun4
-     ../gdb-4.9/configure sun4
+     ../gdb-4.12/configure sun4
      make
 
    When `configure' builds a configuration using a remote source
@@ -258,8 +258,8 @@ called `configure' (or one of its subdirectories).
 
    The `Makefile' that `configure' generates in each source directory
 also runs recursively.  If you type `make' in a source directory such
-as `gdb-4.9' (or in a separate configured directory configured with
-`--srcdir=PATH/gdb-4.9'), you will build all the required libraries,
+as `gdb-4.12' (or in a separate configured directory configured with
+`--srcdir=PATH/gdb-4.12'), you will build all the required libraries,
 and then build GDB.
 
    When you have multiple hosts or targets configured in separate
@@ -302,7 +302,7 @@ you can use it to test your guesses on abbreviations--for example:
      Invalid configuration `i786v': machine `i786v' not recognized
 
 `config.sub' is also distributed in the GDB source directory
-(`gdb-4.9', for version 4.9).
+(`gdb-4.12', for version 4.12).
 
 
 `configure' options
@@ -370,20 +370,7 @@ GDB or its supporting libraries.
 Languages other than C
 =======================
 
-GDB provides some support for debugging C++ programs, however that support
-only works well with GNU C++, and even then only on systems that use stabs
-debugging format.  In particular, cfront based compilers such as Sun's C++
-are not fully supported.
-
-GDB should work with FORTRAN programs.  If you have problems, please send a
-bug report; you may have to refer to some FORTRAN variables with a trailing
-underscore.
-
-Pascal programs which use sets, subranges, file variables, or nested functions
-will not currently work.
-
-Partial Modula-2 and Chill support is now in GDB.
-
+See the GDB manual (doc/gdb.texinfo) for information on this.
 
 Kernel debugging
 =================
@@ -440,7 +427,7 @@ Reporting Bugs
 The correct address for reporting bugs found in gdb is
 "bug-gdb@prep.ai.mit.edu".  Please email all bugs, and all requests for
 help with GDB, to that address.  Please include the GDB version number
-(e.g. gdb-4.9), and how you configured it (e.g. "sun4" or "mach386
+(e.g. gdb-4.12), and how you configured it (e.g. "sun4" or "mach386
 host, i586-intel-synopsys target").  If you include the banner that GDB
 prints when it starts up, that will give us enough information.
 
@@ -478,8 +465,20 @@ Known bugs:
     It has been reported that the Ultrix 4.3A compiler on decstations has the
     same problems.
 
-    If you compile gdb with gcc-2.4.5, you will get many warnings,
-    but these can be ignored for now.  Again, this problem is Alpha-specific.
+    Under some circumstances OSF/1 shared libraries do get relocated to a
+    different address, but gdb cannot handle these relocations yet. If you
+    encounter problems while debugging executables which use shared libraries,
+    try to relink your executable with the -non_shared option when using cc
+    or with the -static option when using gcc.
+
+  * Notes for BSD/386:
+    To compile gdb-4.12 on BSD/386, you must run the configure script and
+    its subscripts with bash.  Here is an easy way to do this:
+
+	bash -c 'CONFIG_SHELL=/bin/bash ./configure'
+
+    (configure will report i386-unknown-bsd).  Then, compile with the
+    standard "make" command.
 
 GDB can produce warnings about symbols that it does not understand.  By
 default, these warnings are disabled.  You can enable them by executing
@@ -531,20 +530,20 @@ The testsuite is distributed separately from the base gdb distribution
 for the convenience of people that wish to get either gdb or the testsuite
 separately.
 
-The name of the testsuite is gdb-4.9-testsuite.tar.z.  You unpack it in the
+The name of the testsuite is gdb-4.12-testsuite.tar.gz.  You unpack it in the
 same directory in which you unpacked the base gdb distribution, and it
-will create and populate the directory gdb-4.9/gdb/testsuite.
+will create and populate the directory gdb-4.12/gdb/testsuite.
 
 Running the testsuite requires the prior installation of dejagnu, which
 should be available via ftp.  Once dejagnu is installed, you can run
 the tests in one of two ways:
 
-  (1)	cd gdb-4.9/gdb		(assuming you also unpacked gdb)
+  (1)	cd gdb-4.12/gdb		(assuming you also unpacked gdb)
 	make check
 
 or
 
-  (2)	cd gdb-4.9/gdb/testsuite
+  (2)	cd gdb-4.12/gdb/testsuite
 	make		(builds the test executables)
 	make site.exp	(builds the site specific file)
 	runtest -tool gdb GDB=../gdb    (or GDB=<somepath> as appropriate)