Re: [PATCH] GDB command-line switches and annotations docs

[Jim Kingdon <kingdon@redhat.com>]

> +@c NOTE: the @cindex entries here use double dashes (actually, triple
> +@c dashes, but that's because of makeinfo formatting of indices) ON

The way to handle the makeinfo formatting issue is "@cindex
@code{--test}" rather than "@cindex ---test"; the latter is an em dash
in the printed manual rather than two "-" characters.  I just tried
the former in both info and TeX and it seems to do the right thing.

> +@cindex ---quite

Typo ("quite" should be "quiet").

Other than that I didn't see problems.
From msnyder@cygnus.com Sat Apr 01 00:00:00 2000
From: Michael Snyder <msnyder@cygnus.com>
To: Jim Kingdon <kingdon@redhat.com>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: Patch to fix thread support for Solaris x86
Date: Sat, 01 Apr 2000 00:00:00 -0000
Message-id: <38BBEDF4.620@cygnus.com>
References: <200002261228.NAA32377@reisser.regent.e-technik.tu-muenchen.de> <bem9ypm2a.fsf@rtl.cygnus.com>
X-SW-Source: 2000-q1/msg00430.html
Content-length: 491

Jim Kingdon wrote:
> 
> > This patch fixes thread support for Solaris x86 platforms.
> 
> Looks like a straightforward bug fix.
> 
> Maintainer, as with the other Solaris x86 patch, currently unknown.  I
> like Kevin Buettner's suggestion of appointing a generic x86
> maintainer, if we can find a victim.

This is a sol-thread issue and relates directly to the 
thread work I was doing recently.  I'll approve it pro tem, 
and look at it more closely when I get back to that work.

Michael
From kingdon@redhat.com Sat Apr 01 00:00:00 2000
From: Jim Kingdon <kingdon@redhat.com>
To: gdb-patches@sourceware.cygnus.com
Subject: Re: GDB 5.0 2000-03-05
Date: Sat, 01 Apr 2000 00:00:00 -0000
Message-id: <br9dojaan.fsf@rtl.cygnus.com>
References: <38C2320A.E2134B29@cygnus.com> <20000305094341.A10426@lucon.org>
X-SW-Source: 2000-q1/msg00538.html
Content-length: 1587

> Linux people are looking for something better than gdb 4.17.0.1x to
> debug Linuxthreads. It will be very disappointing if 5.0 fails to do
> so.

True, it would be disappointing.  Anyway, here is my attempt to
summarize what is up with Linux (based of course on
http://sourceware.cygnus.com/gdb/issues50.html ).  In case it isn't
obvious, it is up to Linux folks (HJ/JimB/MarkK/me/whoever to) get
fixes checked in, we don't want to keep "5.0 release central" (Andrew)
waiting.

* Spurious SIGTRAP bug.  No one has diagnosed this bug as far as I
  know, although JimB was working on it.  This one is probably the most
  serious.

* lin-thread cannot handle thread exit.  Should we think about
  disabling lin-thread in favor of linux-thread for 5.0?  Or to put it
  another way, has lin-thread gotten enough testing?  There might
  be other variations on this theme, such as a note in the
  documentation about how deleting/renaming libthread_db might be a
  workaround, although I'm not sure that really helps much.

* dlclose().  Any reactions MarkK?  Or JimB?  Note that issues50.html
  points to a withdrawn patch; the most recent is:
  http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00454.html

* 2.0.x kernel patch.  MarkK?  issues50.html points to the latest
  patch on this as far as I know:
  http://sourceware.cygnus.com/ml/gdb-patches/1999-q4/msg00294.html

* hardware watchpoints.  Does not strike me as important for 5.0 as
  the above, but if someone has time, should be worth a review.  It is
  nice to see some patches out there.
From ahobson@eng.mindspring.net Sat Apr 01 00:00:00 2000
From: Andrew Hobson <ahobson@eng.mindspring.net>
To: gdb-patches@sourceware.cygnus.com
Subject: PATCH for alphaev56-dec-osf5.0: MERGEPID undefined
Date: Sat, 01 Apr 2000 00:00:00 -0000
Message-id: <kjvh3yxd4l.fsf@gamma.eng.mindspring.net>
X-SW-Source: 2000-q1/msg00104.html
Content-length: 1256

I checked out gdb 5.0 from CVS today and found a minor compilation
issue.  In procfs.c, I find:


/* Provide default composite pid manipulation macros for systems that
   don't have threads. */

#ifndef PIDGET
#define PIDGET(PID)             (PID)
#define TIDGET(PID)             (PID)
#define MERGEPID(PID, TID)      (PID)
#endif


... but in defs.h I find:

/* On some systems, PIDGET is defined to extract the inferior pid from
   an internal pid that has the thread id and pid in seperate bit
   fields.  If not defined, then just use the entire internal pid as
   the actual pid. */

#ifndef PIDGET
#define PIDGET(PID) (PID)
#define TIDGET(PID) 0
#endif


That leaves MERGEPID undefined.  I'm not positive of the correct fix,
but the following patch solves the problem for me.

Drew

Index: defs.h
===================================================================
RCS file: /cvs/src/src/gdb/defs.h,v
retrieving revision 1.1.1.31
diff -u -p -r1.1.1.31 defs.h
--- defs.h	2000/02/05 07:29:41	1.1.1.31
+++ defs.h	2000/02/09 20:52:56
@@ -1218,6 +1218,7 @@ extern int use_windows;
 #ifndef PIDGET
 #define PIDGET(PID) (PID)
 #define TIDGET(PID) 0
+#define MERGEPID(PID, TID) (PID)
 #endif
 
 /* If under Cygwin, provide backwards compatibility with older
From fnasser@redhat.com Sat Apr 01 00:00:00 2000
From: Fernando Nasser <fnasser@redhat.com>
To: dan@cgsoftware.com
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: [RFC] Patch to add apropos command
Date: Sat, 01 Apr 2000 00:00:00 -0000
Message-id: <38D0FB27.5682007D@redhat.com>
References: <4sa7j7bm.fsf@dan.resnet.rochester.edu>
X-SW-Source: 2000-q1/msg00743.html
Content-length: 1904

Daniel,

I haven't looked at the patch proper (lets leave the implementation
details aside for a moment), but the idea is really nice.

A few weeks ago I posted something about improving the help command. 
Some users were asking for a "help all" command.  My guess is that what
they really want is an apropos, they just intended to do it visually,
but I guess they will be trilled by an apropos command.

Let's see what other people say, by I believe it is a really nice idea.

Fernando


"Daniel Berlin+list.gdb-patches" wrote:
> 
> Attached is a patch that adds a simple, functional, apropos for gdb.
> 
> it searchs all command names and command doc strings (case
> insensitively)
> for the regex ".*<searchstr>.*".
> 
> It's not perfect, error checking is a bit lax, it just does nothing
> when errors happen, rather than print out the error message.
> It's also a little slower than i want it to be.
> But it does search the name and docstring of every command, and
> properly prints out the command and docstrings of the matching ones.
> It also double prints if the name and docstring both match.
> And if we are searching through a prefix, i really should have it
> print out the prefix as well.
> I'm sure i could think of a better regex too.
> 
> But, even given all that, it's pretty useful, even in current form.
> 
> I wanted to get some comments about usefulness before i go extending
> it.
> I'll happily make it do whatever people want.
> 
>   ------------------------------------------------------------------------
> 
>    apropos.diffName: apropos.diff
>                Type: text/x-patch
> 
>   ------------------------------------------------------------------------

-- 
Fernando Nasser
Red Hat, Inc. - Toronto                 E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300           Tel:  416-482-2661 ext. 311
Toronto, Ontario   M4P 2C9              Fax:  416-482-6299
From ac131313@cygnus.com Sat Apr 01 00:00:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: BINUTILS Patches <binutils@sourceware.cygnus.com>, GDB Patches <gdb-patches@sourceware.cygnus.com>
Subject: Re: [PATCH RFA] Clean up GDB's packaging, add support for dejagnu, insight, ...
Date: Sat, 01 Apr 2000 00:00:00 -0000
Message-id: <38BF746B.6B8F1253@cygnus.com>
References: <38BF6FEB.F1354790@cygnus.com>
X-SW-Source: 2000-q1/msg00467.html
Content-length: 4311

Andrew Cagney wrote:

Sorry, I'll try that again.  It would be attatched....
(Kevin, thanks :-)

> Hello,
> 
> The attatched patch modifies the top level Makefile.in so that:
> 
>         o       the ``taz:'' / ``do-tar-bz2:'' targets
>                 build a PACKAGE instead of a TOOL.
>                 By default PACKAGE=$(TOOL)
>                 The PACKAGE determines the archive
>                 name while the TOOL determines the
>                 top level directory containing
>                 versioning etc.
> 
>         o       Removes GDBTK stuff from the GDB
>                 net relese
> 
>         o       adds rules to build ``dejagnu''
>                 ``gdb+dejagnu'' ``insight''
>                 and ``insight+dejagnu'' releases
> 
> Ok?

         Andrew
Fri Mar  3 18:44:08 2000  Andrew Cagney  <cagney@b1.cygnus.com>

	* Makefile.in (taz): Set PACKAGE to TOOL when not defined.
	(do-tar-bz2): Replace TOOL with PACKAGE.
	(gdb.tar.bz2): Remove GDBTK from GDB package.
	(gdb+dejagnu.tar.bz2, insight.tar.bz2, insight+dejagnu.tar.bz2,
 	dejagnu.tar.bz2): New packages.

Index: Makefile.in
===================================================================
RCS file: /cvs/src/src/Makefile.in,v
retrieving revision 1.8
diff -p -r1.8 Makefile.in
*** Makefile.in	2000/02/07 00:34:34	1.8
--- Makefile.in	2000/03/03 08:13:08
*************** taz: $(DEVO_SUPPORT) $(SUPPORT_FILES) te
*** 1747,1760 ****
  	else \
  	  ver=`sed <$(TOOL)/Makefile.in -n 's/^VERSION *= *//p'`; \
  	fi; \
! 	$(MAKE) -f Makefile.in do-tar-bz2 TOOL=$(TOOL) VER=$$ver
  
  do-tar-bz2:
! 	echo "==> Making $(TOOL)-$(VER).tar.bz2"
! 	-rm -f $(TOOL)-$(VER)
! 	ln -s proto-toplev $(TOOL)-$(VER)
! 	tar cfh $(TOOL)-$(VER).tar $(TOOL)-$(VER)
! 	$(BZIPPROG) -v -9 $(TOOL)-$(VER).tar
  
  TEXINFO_SUPPORT= texinfo/texinfo.tex
  DIST_SUPPORT= $(DEVO_SUPPORT) $(TEXINFO_SUPPORT)
--- 1747,1765 ----
  	else \
  	  ver=`sed <$(TOOL)/Makefile.in -n 's/^VERSION *= *//p'`; \
  	fi; \
! 	if test x"$(PACKAGE)" = x; then \
! 	  package="$(TOOL)"; \
! 	else \
! 	  package="$(PACKAGE)"; \
! 	fi; \
! 	$(MAKE) -f Makefile.in do-tar-bz2 TOOL=$(TOOL) VER=$$ver PACKAGE=$$package
  
  do-tar-bz2:
! 	echo "==> Making $(PACKAGE)-$(VER).tar.bz2"
! 	-rm -f $(PACKAGE)-$(VER)
! 	ln -s proto-toplev $(PACKAGE)-$(VER)
! 	tar cfh $(PACKAGE)-$(VER).tar $(PACKAGE)-$(VER)
! 	$(BZIPPROG) -v -9 $(PACKAGE)-$(VER).tar
  
  TEXINFO_SUPPORT= texinfo/texinfo.tex
  DIST_SUPPORT= $(DEVO_SUPPORT) $(TEXINFO_SUPPORT)
*************** gnats.tar.bz2: $(DIST_SUPPORT) $(GNATS_S
*** 1791,1800 ****
  
  .PHONY: gdb.tar.bz2
  GDB_SUPPORT_DIRS= bfd include libiberty mmalloc opcodes readline sim utils intl
- GDBTK_SUPPORT_DIRS= `if [ -d tcl -a -d tk ] ; then echo tcl tk itcl tix libgui; fi`
  gdb.tar.bz2: $(DIST_SUPPORT) $(GDB_SUPPORT_DIRS) gdb
  	$(MAKE) -f Makefile.in taz TOOL=gdb \
! 		SUPPORT_FILES="$(GDB_SUPPORT_DIRS) $(GDBTK_SUPPORT_DIRS)"
  
  .PHONY: newlib.tar.bz2
  NEWLIB_SUPPORT_DIRS=libgloss
--- 1796,1828 ----
  
  .PHONY: gdb.tar.bz2
  GDB_SUPPORT_DIRS= bfd include libiberty mmalloc opcodes readline sim utils intl
  gdb.tar.bz2: $(DIST_SUPPORT) $(GDB_SUPPORT_DIRS) gdb
  	$(MAKE) -f Makefile.in taz TOOL=gdb \
! 		SUPPORT_FILES="$(GDB_SUPPORT_DIRS)"
! 
! .PHONY: dejagnu.tar.bz2
! DEJAGNU_SUPPORT_DIRS=  tcl expect libiberty
! dejagnu.tar.bz2: $(DIST_SUPPORT) $(DEJAGNU_SUPPORT_DIRS) dejagnu
! 	$(MAKE) -f Makefile.in taz TOOL=dejagnu \
! 		SUPPORT_FILES="$(DEJAGNU_SUPPORT_DIRS)"
! 
! .PHONY: gdb+dejagnu.tar.bz2
! GDBD_SUPPORT_DIRS= $(GDB_SUPPORT_DIRS) tcl expect dejagnu
! gdb+dejagnu.tar.bz2: $(DIST_SUPPORT) $(GDBD_SUPPORT_DIRS) gdb
! 	$(MAKE) -f Makefile.in taz TOOL=gdb PACKAGE=gdb+dejagnu \
! 		SUPPORT_FILES="$(GDBD_SUPPORT_DIRS)"
! 
! .PHONY: insight.tar.bz2
! INSIGHT_SUPPORT_DIRS= $(GDB_SUPPORT_DIRS) tcl tk itcl tix libgui
! insight.tar.bz2: $(DIST_SUPPORT) $(GDB_SUPPORT_DIRS) gdb
! 	$(MAKE) -f Makefile.in taz TOOL=gdb PACKAGE=insight \
! 		SUPPORT_FILES="$(INSIGHT_SUPPORT_DIRS)"
! 
! .PHONY: insight+dejagnu.tar.bz2
! INSIGHTD_SUPPORT_DIRS= $(INSIGHT_SUPPORT_DIRS) expect dejagnu
! insight+dejagnu.tar.bz2: $(DIST_SUPPORT) $(INSIGHTD_SUPPORT_DIRS) gdb
! 	$(MAKE) -f Makefile.in taz TOOL=gdb PACKAGE="insight+dejagnu" \
! 		SUPPORT_FILES="$(INSIGHTD_SUPPORT_DIRS)"
  
  .PHONY: newlib.tar.bz2
  NEWLIB_SUPPORT_DIRS=libgloss
From ac131313@cygnus.com Sat Apr 01 00:00:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: GDB Patches <gdb-patches@sourceware.cygnus.com>
Subject: [PATCH] Fix configure.in typo - ``{'' vs ``(''
Date: Sat, 01 Apr 2000 00:00:00 -0000
Message-id: <38B4DC8A.543E5594@cygnus.com>
X-SW-Source: 2000-q1/msg00352.html
Content-length: 1118

FYI,

I've committed the attatched.  It stopped configure --enable-gdbmi from
building in a really wierd way.

	Andrew
Thu Feb 24 18:19:52 2000  Andrew Cagney  <cagney@b1.cygnus.com>

	* configure.in (SUBDIR_MI_CFLAGS): Fix typo, wrong brace.
	* configure: Regenerate.
	
Index: configure.in
===================================================================
RCS file: /cvs/src/src/gdb/configure.in,v
retrieving revision 1.5
diff -p -r1.5 configure.in
*** configure.in	2000/02/23 00:25:42	1.5
--- configure.in	2000/02/24 07:21:24
*************** case ${enable_gdbmi} in
*** 384,390 ****
        CONFIG_DEPS="${CONFIG_DEPS} \$(SUBDIR_MI_DEPS)"
        CONFIG_SRCS="${CONFIG_SRS} \$(SUBDIR_MI_SRCS)"
        CONFIG_INITS="${CONFIG_INITS} \$(SUBDIR_MI_INITS)"
!       ENABLE_CFLAGS="${ENABLE_CFLAGS} \${SUBDIR_MI_CFLAGS)"
      fi
      ;;
  esac
--- 384,390 ----
        CONFIG_DEPS="${CONFIG_DEPS} \$(SUBDIR_MI_DEPS)"
        CONFIG_SRCS="${CONFIG_SRS} \$(SUBDIR_MI_SRCS)"
        CONFIG_INITS="${CONFIG_INITS} \$(SUBDIR_MI_INITS)"
!       ENABLE_CFLAGS="${ENABLE_CFLAGS} \$(SUBDIR_MI_CFLAGS)"
      fi
      ;;
  esac
From fnasser@redhat.com Sat Apr 01 00:00:00 2000
From: Fernando Nasser <fnasser@redhat.com>
To: gdb-patches@sourceware.cygnus.com
Subject: RFC: Targets that do not call generic_mourn_inferior() ?
Date: Sat, 01 Apr 2000 00:00:00 -0000
Message-id: <38B40D27.36766187@redhat.com>
X-SW-Source: 2000-q1/msg00337.html
Content-length: 1701

It seems to me that, except for very exceptional circustances, all
remote targets should be calling generic_mourn_inferior().  It does some
gdb cleanup that is necessary if the user ever reconnects to the target
within the same session.

An alternative is to have gdb forcifully calling this when unpushing a
target, but the current way is more flexible (and more error prone as
well).

Here is a patch for two targets that missed that call and act very silly
if one does a "I reg" or "bt" after reconnecting.

-- 
Fernando Nasser
Red Hat, Inc. - Toronto                 E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300           Tel:  416-482-2661 ext. 311
Toronto, Ontario   M4P 2C9              Fax:  416-482-6299


Index: remote-rdi.c
===================================================================
RCS file: /cvs/src/src/gdb/remote-rdi.c,v
retrieving revision 1.2
diff -c -p -r1.2 remote-rdi.c
*** remote-rdi.c        2000/02/09 08:52:47     1.2
--- remote-rdi.c        2000/02/23 16:28:24
*************** arm_rdi_close (quitting)
*** 462,467 ****
--- 462,468 ----
        closed_already = 1;
        inferior_pid = 0;
        Adp_CloseDevice ();
+       generic_mourn_inferior ();
      }
  }
  
Index: remote-sim.c
===================================================================
RCS file: /cvs/src/src/gdb/remote-sim.c,v
retrieving revision 1.2
diff -c -p -r1.2 remote-sim.c
*** remote-sim.c        2000/02/09 08:52:47     1.2
--- remote-sim.c        2000/02/23 16:28:24
*************** gdbsim_close (quitting)
*** 560,565 ****
--- 560,566 ----
      }
  
    end_callbacks ();
+   generic_mourn_inferior ();
  }
  
  /* Takes a program previously attached to and detaches it.
From eliz@delorie.com Sat Apr 01 00:00:00 2000
From: Eli Zaretskii <eliz@delorie.com>
To: gdb-patches@sourceware.cygnus.com
Subject: [PATCH] Support for building with DJGPP
Date: Sat, 01 Apr 2000 00:00:00 -0000
Message-id: <200003191224.HAA08367@indy.delorie.com>
X-SW-Source: 2000-q1/msg00783.html
Content-length: 26903

I committed today the following patches which allow to build GDB with
DJGPP tools.

2000-03-17  Eli Zaretskii  <eliz@is.elta.co.il>

	* config/djgpp/djconfig.sh: New file.
	* config/djgpp/config.sed: New file.
	* config/djgpp/README: New file.
	* config/djgpp/fnchange.lst: New file.
	* config/djgpp/djcheck.sh: New file.


--- /dev/null	Fri Mar 17 19:01:45 2000
+++ gdb/config/djgpp/djconfig.sh	Fri Mar 17 11:54:06 2000
@@ -0,0 +1,127 @@
+#!/bin/sh
+# 
+# This shell script is a wrapper to the main configure script when
+# configuring GDB for DJGPP.  99% of it can also be used when
+# configuring other GNU programs for DJGPP.
+#
+# Originally written by Robert Hoehne, revised by Eli Zaretskii.
+#
+# Call it like the main configure script with one exception.  If you
+# want to pass parameters to configure, you have to pass as the first
+# argument the srcdir, even when it is `.' !!!!!
+
+# Where are the sources? If you are used to having the sources
+# in a separate directory and the objects in another, then set
+# here the full path to the source directory and run this script
+# in the directory where you want to build gdb!!
+# You might give the source directory on commandline, but use
+# then only forward slashes (/) in the directories. It should be
+# an absolute path.
+
+if [ x$1 = x ]; then
+  srcdir=`pwd`
+else
+  srcdir=`cd $1 && pwd`
+  shift
+fi
+
+# Make sure they don't have some file names mangled by untarring.
+echo -n "Checking the unpacked distribution..."
+if ( ! test -f ${srcdir}/intl/po2tblsed.in || \
+     ! test -d ${srcdir}/gdb/testsuite/gdb.cxx || \
+     ! test -f ${srcdir}/readline/config.h-in ) ; then
+  echo " FAILED."
+  echo ""
+  echo "You MUST unpack the sources with the DJTAR command, like this:"
+  echo ""
+  echo "         djtar -x -n fnchange.lst gdb-X.YZ.tar.gz"
+  echo ""
+  echo "where X.YZ is the GDB version, and fnchange.lst can be found"
+  echo "in the gdb/config/djgpp/ directory in the GDB distribution."
+  echo "configure FAILED!"
+  exit 1
+else
+  echo " ok."
+fi
+
+# Where is the directory with DJGPP-specific scripts?
+DJGPPDIR=${srcdir}/gdb/config/djgpp
+
+echo "Editing configure scripts for DJGPP..."
+TMPFILE="${TMPDIR-.}/cfg.tmp"
+
+# We need to skip the build directory if it is a subdirectory of $srcdir,
+# otherwise we will have an infinite recursion on our hands...
+if test "`pwd`" == "${srcdir}" ; then
+  SKIPDIR=""
+  SKIPFILES=""
+else
+  SKIPDIR=`pwd | sed -e "s|${srcdir}|.|"`
+  SKIPFILES="${SKIPDIR}/*"
+fi
+for fix_dir in \
+  `cd $srcdir && find . -type d ! -ipath "${SKIPDIR}" ! -ipath "${SKIPFILES}"`
+do
+  if test ! -f ${fix_dir}/configure.orig ; then
+    if test -f ${srcdir}/${fix_dir}/configure ; then
+      mkdir -p ${fix_dir}
+      cp -p ${srcdir}/${fix_dir}/configure ${fix_dir}/configure.orig
+    fi
+  fi
+  if test -f ${fix_dir}/configure.orig ; then
+    sed -f ${DJGPPDIR}/config.sed ${fix_dir}/configure.orig > $TMPFILE
+    update $TMPFILE ${fix_dir}/configure
+    touch ./${fix_dir}/configure -r ${fix_dir}/configure.orig
+    rm -f $TMPFILE
+  fi
+  if test -f ${fix_dir}/INSTALL ; then
+    mv ${fix_dir}/INSTALL ${fix_dir}/INSTALL.txt
+  fi
+done
+
+# Now set the config shell. It is really needed, that the shell
+# points to a shell with full path and also it must conatain the
+# .exe suffix. I assume here, that bash is installed. If not,
+# install it. Additionally, the pathname must not contain a
+# drive letter, so use the /dev/x/foo format supported by versions
+# of Bash 2.03 and later, and by all DJGPP programs compiled with
+# v2.03 (or later) library.
+export CONFIG_SHELL=/dev/env/DJDIR/bin/sh.exe
+
+# force to have the ltmain.sh script to be in DOS text format,
+# otherwise the resulting ltconfig script will have mixed
+# (UNIX/DOS) format and is unusable with Bash ports before v2.03.
+utod $srcdir/ltmain.sh
+
+# Give the configure script some hints:
+export LD=ld
+export CC=gcc
+export RANLIB=ranlib
+export DEFAULT_YACC="bison -y"
+export YACC="bison -y"
+export DEFAULT_LEX=flex
+# Define explicitly the .exe extension because on W95 with LFN=y
+# the check might fail
+export am_cv_exeext=.exe
+
+# The configure script needs to see the `install-sh' script, otherwise
+# it decides the source installation is broken.  But "make install" will
+# fail on 8+3 filesystems if it finds a file `install-', since there
+# are numerous "install-foo" targets in Makefile's.  So we rename the
+# offending file after the configure step is done.
+if test ! -f ${srcdir}/install-sh ; then
+  if test -f ${srcdir}/install-.sh ; then
+    mv ${srcdir}/install-.sh ${srcdir}/install-sh
+  fi
+fi
+
+# Now run the configure script while disabling some things like the NLS
+# support, which is nearly impossible to be supported in the current way,
+# since it relies on file names which will never work on DOS.
+echo "Running the configure script..."
+$srcdir/configure --srcdir="$srcdir" --prefix='${DJDIR}' \
+  --disable-shared --disable-nls --verbose $*
+
+if test -f ${srcdir}/install- ; then
+  mv ${srcdir}/install- ${srcdir}/install-.sh
+fi
--- /dev/null	Fri Mar 17 19:02:11 2000
+++ gdb/config/djgpp/config.sed	Fri Mar 17 17:19:26 2000
@@ -0,0 +1,30 @@
+s|po2tbl\.sed\.in|po2tblsed.in|g
+s|gdb\.c++|gdb.cxx|g
+/ac_rel_source/s|ln -s|cp -p|
+s|\.gdbinit|gdb.ini|g
+
+/ac_given_INSTALL=/,/^CEOF/ {
+  /^s%@prefix@%/a\
+  s,\\([yp*]\\)\\.tab,\\1_tab,g\
+  /^	@rm -f/s,\\$@-\\[0-9\\]\\[0-9\\],&$*.i[1-9] $*[1-9][0-9],\
+  s,\\.info\\*,.inf* *.i[1-9] *.i[1-9][0-9],\
+  s,\\.gdbinit,gdb.ini,g\
+  /TEXINPUTS=/s,:,';',g\
+  /VPATH *=/s,:,;,g\
+  /\\$\\$file-\\[0-9\\]/s,echo,& *.i[1-9] *.i[1-9][0-9],\
+  s,config\\.h\\.in,config.h-in,g\
+  s,po2tbl\\.sed\\.in,po2tblsed.in,g
+}
+
+/^CONFIG_FILES=/,/^EOF/ {
+  s|po/Makefile.in\([^-:]\)|po/Makefile.in:po/Makefile.in-in\1|
+}
+
+/^ *CONFIG_HEADERS=/,/^EOF/ {
+  s|config.h\([^-:]\)|config.h:config.h-in\1|
+}
+
+/^[ 	]*\/\*)/s,/\*,/*|[A-z]:/*,
+/\$]\*) INSTALL=/s,\[/\$\]\*,&|[A-z]:/*,
+/\$]\*) ac_rel_source=/s,\[/\$\]\*,&|[A-z]:/*,
+/ac_file_inputs=/s,\( -e "s%\^%\$ac_given_srcdir/%"\)\( -e "s%:% $ac_given_srcdir/%g"\),\2\1,
--- /dev/null	Fri Mar 17 20:41:18 2000
+++ gdb/config/djgpp/README	Fri Mar 17 20:40:54 2000
@@ -0,0 +1,172 @@
+
+       How to build and install the DJGPP native version of GDB
+       ********************************************************
+
+General
+=======
+
+GDB built with DJGPP supports native DJGPP debugging, whereby you run
+gdb.exe and the program being debugged on the same machine.  In
+addition, this version supports remote debugging via a serial port,
+provided that the target machine has a GDB-compatible debugging stub
+which can be linked with the target program (see the section "Remote
+Serial" in the GDB manual for more details).
+
+
+Installation of the binary distribution
+=======================================
+
+Simply unzip the gdbNNNb.zip file (where NNN is the version number)
+from the top DJGPP installation directory.  Be sure to preserve the
+directory structure while you unzip (use -d switch if you do this with
+PKUNZIP).  On Windows 9X and Windows 2000, use an unzip program which
+supports long file names; one such program is unzip32.exe, available
+from the DJGPP sites.
+
+If you need the libraries which are built as part of GDB, install the
+companion file gdbNNNa.zip.  This allows to develop applications which
+use the same functions as GDB.  For example, you can build your own
+front end to the debugger.
+
+
+Rebuilding GDB from sources
+===========================
+
+1. Prerequisites
+   -------------
+To build the package, you will need the DJGPP development environment
+(GCC, header files, and the libraries), and also DJGPP ports of the
+following tools:
+
+	- GNU Make 3.78.1 or later
+	- Bash 2.03 or later
+	- GNU Sed
+	- GNU Fileutils
+	- GNU Textutils 2.0 or later
+	- GNU Sh-utils
+	- GNU Grep 2.4 or later
+	- GNU Findutils
+	- GNU Awk 3.04 or later
+	- GNU Bison (only if you change one of the gdb/*.y files)
+	- Groff (only if you need to format the man pages)
+	- GNU Diffutils (only if you run the test suite)
+
+These programs should be available from the DJGPP sites, in the v2gnu
+directory.  In addition, the configuration script invokes the `update'
+and `utod' utilities which are part of the basic DJGPP development kit
+(djdevNNN.zip).
+
+
+2. Unpacking the sources
+   ---------------------
+If you download the source distribution from one of the DJGPP sites,
+just unzip it while preserving the directory structure (I suggest to
+use unzip32.exe available with the rest of DJGPP), and proceed to the
+section "How to build" below.
+
+Source distributions downloaded from one of the GNU FTP sites need
+some more work to unpack.  First, you MUST use the `djtar' program to
+unzip the package.  That's because some file names in the official
+distributions need to be changed to avoid problems on the various
+platforms supported by DJGPP.  `djtar' can rename files on the fly
+given a file with name mappings; the distribution includes a file
+`gdb/config/djgpp/fnchange.lst' with the necessary mappings.  So you
+need first to retrieve that file, and then invoke `djtar' to unpack
+the distribution.  Here's how:
+
+
+ djtar -x -p -o gdb-5.0/gdb/config/djgpp/fnchange.lst gdb-5.0.tar.gz > lst
+ djtar -x -n lst gdb-5.0.tar.gz
+
+(The name of the distribution archive and the top-level directory will
+be different for versions other than 5.0.)
+
+
+3. How to build
+   ------------
+
+The source distribution available from DJGPP archives is already
+configured for DJGPP v2.x, so if you only want to compile it, just
+invoke Make:
+
+		make
+
+To build a package downloaded from a GNU FTP site, you will need o
+configure it first.  You will also need to configure it if you want to
+change the configuration options (e.g., compile with support for the
+GDBMI interface).  To configure GDB, type this command:
+
+		sh ./gdb/config/djgpp/djconfig.sh
+
+This script checks the unpacked distribution, then edits the configure
+scripts in the various subdirectories, to make them suitable for
+DJGPP, and finally invokes the top-level configure script, which
+recursively configures all the subdirectories.
+
+You may pass optional switches to djconfig.sh.  It accepts all the
+switches accepted by the original GDB configure script.  These
+switches are described in the file gdb/README, and their full list be
+displayed by running the following command:
+
+		sh ./gdb/configure --help
+
+NOTE: if you *do* use optional command-line switches, you MUST pass
+to the script the name of the directory where GDB sources are
+unpacked--even if you are building GDB in-place!  For example:
+
+	sh ./gdb/config/djgpp/djconfig.sh . --enable-gdbmi
+
+It is also possible to build GDB in a directory that is different from
+the one where the sources were unpacked.  In that case, you have to
+pass the source directory as the first argument to the script:
+
+	sh ./gdb/config/djgpp/djconfig.sh d:/gnu/gdb-5.0
+
+You MUST use forward slashes in the first argument.
+
+After the configure script finishes, run Make:
+
+	make
+
+When Make finishes, you can install the package:
+
+	make install INSTALL='/dev/env/DJDIR/bin/ginstall -c'
+
+The above doesn't install the docs; for that you will need to say
+this:
+
+	make -k install-info INSTALL='/dev/env/DJDIR/bin/ginstall -c'
+
+(The -k switch is required, because some unneeded targets that are
+part of the install process fail; -k lets Make run to completion
+nonetheless.)
+
+The test suite has been made to work with DJGPP.  If you make a change
+in some of the programs, or want to be sure you have a fully
+functional GDB executable, it is a good idea to run the test suite.
+You cannot use "make check" for that, since it will want to run the
+`dejagnu' utility which GDB doesn't support.  Instead, use the special
+script gdb/config/djgpp/djcheck.sh, like this:
+
+		cd gdb/testsuite
+		sh ../config/djgpp/djcheck.sh
+
+This will run for a while and should not print anything.  Any test
+that fails to produce the expected output will cause the diffs between
+the expected and the actual output be printed, and in addition will
+leave behind a file SOMETHING.tst (where SOMETHING is the name of one
+of the tests).  You should compare each of the *.tst files with the
+corresponding *.out file and convince yourself that the differences do
+not indicate a real problem.  Examples of differences you can
+disregard are changes in the copyright blurb printed by GDB, values of
+unitialized variables, addresses of global variables like argv[] and
+envp[] (which depend on the size of your environment), etc.
+
+Note that djcheck.sh only recurses into those of the subdirectories of
+the test suite which test features supported by the DJGPP port of GDB.
+For example, the tests in the gdb.gdbtk, gdb.threads, and gdb.hp
+directories are not run.
+
+
+Enjoy,
+                                    Eli Zaretskii <eliz@is.elta.co.il>
--- /dev/null	Fri Mar 17 20:46:50 2000
+++ gdb/config/djgpp/fnchange.lst	Fri Mar 17 20:46:08 2000
@@ -0,0 +1,176 @@
+gdb-0222/gdb/ChangeLog-3.x gdb-0222/gdb/ChangeLog.3-x
+gdb-0222/gdb/ChangeLog-9091 gdb-0222/gdb/ChangeLog.9091
+gdb-0222/gdb/ChangeLog-92 gdb-0222/gdb/ChangeLog.92
+gdb-0222/gdb/ChangeLog-93 gdb-0222/gdb/ChangeLog.93
+gdb-0222/gdb/ChangeLog-94 gdb-0222/gdb/ChangeLog.94
+gdb-0222/gdb/ChangeLog-95 gdb-0222/gdb/ChangeLog.95
+gdb-0222/gdb/ChangeLog-96 gdb-0222/gdb/ChangeLog.96
+gdb-0222/gdb/ChangeLog-97 gdb-0222/gdb/ChangeLog.97
+gdb-0222/gdb/ChangeLog-98 gdb-0222/gdb/ChangeLog.98
+gdb-0222/gdb/ChangeLog-99 gdb-0222/gdb/ChangeLog.99
+gdb-0222/gdb/ppc-linux-tdep.c gdb-0222/gdb/ppc-linx-tdep.c
+gdb-0222/gdb/remote-adapt.c gdb-0222/gdb/rmt-adapt.c
+gdb-0222/gdb/remote-array.c gdb-0222/gdb/rmt-array.c
+gdb-0222/gdb/remote-e7000.c gdb-0222/gdb/rmt-e7000.c
+gdb-0222/gdb/remote-eb.c gdb-0222/gdb/rmt-eb.c
+gdb-0222/gdb/remote-es.c gdb-0222/gdb/rmt-es.c
+gdb-0222/gdb/remote-est.c gdb-0222/gdb/rmt-est.c
+gdb-0222/gdb/remote-mips.c gdb-0222/gdb/emt-mips.c
+gdb-0222/gdb/remote-mm.c gdb-0222/gdb/emt-mm.c
+gdb-0222/gdb/remote-nindy.c gdb-0222/gdb/rmt-nindy.c
+gdb-0222/gdb/remote-nrom.c gdb-0222/gdb/rmt-nrom.c
+gdb-0222/gdb/remote-rdi.c gdb-0222/gdb/rmt-rdi.c
+gdb-0222/gdb/remote-rdp.c gdb-0222/gdb/rmt-rdp.c
+gdb-0222/gdb/remote-sds.c gdb-0222/gdb/rmt-sds.c
+gdb-0222/gdb/remote-sim.c gdb-0222/gdb/rmt-sim.c
+gdb-0222/gdb/remote-st.c gdb-0222/gdb/rmt-st.c
+gdb-0222/gdb/remote-udi.c gdb-0222/gdb/rmt-udi.c
+gdb-0222/gdb/remote-vx.c gdb-0222/gdb/rmt-vx.c
+gdb-0222/gdb/remote-vx29k.c gdb-0222/gdb/rmt-vx29k.c
+gdb-0222/gdb/remote-vx68.c gdb-0222/gdb/rmt-vx68.c
+gdb-0222/gdb/remote-vx960.c gdb-0222/gdb/rmt-vx960.c
+gdb-0222/gdb/remote-vxmips.c gdb-0222/gdb/rmt-vxmips.c
+gdb-0222/gdb/remote-vxsparc.c gdb-0222/gdb/rmt-vxsparc.c
+gdb-0222/gdb/sparclet-rom.c gdb-0222/gdb/splet-rom.c
+gdb-0222/gdb/sparclet-stub.c gdb-0222/gdb/splet-stub.c
+gdb-0222/gdb/config/alpha/alpha-osf1.mh gdb-0222/gdb/config/alpha/alphosf1.mh
+gdb-0222/gdb/config/alpha/alpha-osf2.mh gdb-0222/gdb/config/alpha/alphosf2.mh
+gdb-0222/gdb/config/alpha/alpha-osf3.mh gdb-0222/gdb/config/alpha/alphosf3.mh
+gdb-0222/gdb/config/alpha/tm-alphalinux.h gdb-0222/gdb/config/alpha/tm-alplinux.h
+gdb-0222/gdb/config/alpha/xm-alphalinux.h gdb-0222/gdb/config/alpha/xm-alplinux.h
+gdb-0222/gdb/config/i386/nm-i386sco4.h gdb-0222/gdb/config/i386/nm-sco4.h
+gdb-0222/gdb/config/i386/nm-i386sco5.h gdb-0222/gdb/config/i386/nm-sco5.h
+gdb-0222/gdb/config/i386/nm-i386sol2.h gdb-0222/gdb/config/i386/nm-sol2.h
+gdb-0222/gdb/config/i386/nm-i386v4.h gdb-0222/gdb/config/i386/nm-v4.h
+gdb-0222/gdb/config/i386/nm-i386v42mp.h gdb-0222/gdb/config/i386/nm-v42mp.h
+gdb-0222/gdb/config/i386/tm-i386mk.h gdb-0222/gdb/config/i386/tm-mk.h
+gdb-0222/gdb/config/i386/tm-i386sol2.h gdb-0222/gdb/config/i386/tm-sol2.h
+gdb-0222/gdb/config/i386/tm-i386v4.h gdb-0222/gdb/config/i386/tm-v4.h
+gdb-0222/gdb/config/i386/tm-i386v42mp.h gdb-0222/gdb/config/i386/tm-v42mp.h
+gdb-0222/gdb/config/i386/xm-i386mach.h gdb-0222/gdb/config/i386/xm-mach.h
+gdb-0222/gdb/config/i386/xm-i386mk.h gdb-0222/gdb/config/i386/xm-mk.h
+gdb-0222/gdb/config/i386/xm-i386v32.h gdb-0222/gdb/config/i386/xm-v32.h
+gdb-0222/gdb/config/i386/xm-i386v4.h gdb-0222/gdb/config/i386/xm-v4.h
+gdb-0222/gdb/config/m68k/apollo68v.mh gdb-0222/gdb/config/m68k/apollo-v.mh
+gdb-0222/gdb/config/m68k/nm-apollo68v.h gdb-0222/gdb/config/m68k/nm-apolv.h
+gdb-0222/gdb/config/m68k/nm-hp300hpux.h gdb-0222/gdb/config/m68k/nm-300ux.h
+gdb-0222/gdb/config/m68k/tm-hp300hpux.h gdb-0222/gdb/config/m68k/tm-300ux.h
+gdb-0222/gdb/config/m68k/xm-apollo68v.h gdb-0222/gdb/config/m68k/xm-apolv.h
+gdb-0222/gdb/config/m68k/xm-hp300hpux.h gdb-0222/gdb/config/m68k/xm-300ux.h
+gdb-0222/gdb/config/m88k/tm-delta88v4.h gdb-0222/gdb/config/m88k/tm-d88v4.h
+gdb-0222/gdb/config/m88k/xm-delta88v4.h gdb-0222/gdb/config/m88k/xm-d88v4.h
+gdb-0222/gdb/config/mips/tm-bigmips64.h gdb-0222/gdb/config/mips/tm-bigm64.h
+gdb-0222/gdb/config/mips/tm-embed64.h gdb-0222/gdb/config/mips/tm-emb64.h
+gdb-0222/gdb/config/mips/tm-embedl.h gdb-0222/gdb/config/mips/tm-embdl.h
+gdb-0222/gdb/config/mips/tm-embedl64.h gdb-0222/gdb/config/mips/tm-embl64.h
+gdb-0222/gdb/config/mips/tm-vr4300el.h gdb-0222/gdb/config/mips/tm-v43el.h
+gdb-0222/gdb/config/mips/tm-vr4xxxel.h gdb-0222/gdb/config/mips/tm-v4xel.h
+gdb-0222/gdb/config/mips/tm-vr5000el.h gdb-0222/gdb/config/mips/tm-vr5kel.h
+gdb-0222/gdb/config/pa/nm-hppah11.h gdb-0222/gdb/config/pa/nm-hppa11.h
+gdb-0222/gdb/config/powerpc/tm-ppcle-sim.h gdb-0222/gdb/config/powerpc/tm-ppcl-sim.h
+gdb-0222/gdb/config/rs6000/nm-rs6000ly.h gdb-0222/gdb/config/rs6000/nm-rs6kly.h
+gdb-0222/gdb/config/rs6000/tm-rs6000.h gdb-0222/gdb/config/rs6000/tm-rs6k.h
+gdb-0222/gdb/config/rs6000/tm-rs6000ly.h gdb-0222/gdb/config/rs6000/tm-rs6kly.h
+gdb-0222/gdb/config/rs6000/xm-rs6000ly.h gdb-0222/gdb/config/rs6000/xm-rs6kly.h
+gdb-0222/gdb/config/sparc/tm-sparclet.h gdb-0222/gdb/config/sparc/tm-splet.h
+gdb-0222/gdb/config/sparc/tm-sparclite.h gdb-0222/gdb/config/sparc/tm-splite.h
+gdb-0222/gdb/config/sparc/tm-sparclynx.h gdb-0222/gdb/config/sparc/tm-splynx.h
+gdb-0222/gdb/config/sparc/xm-sparclynx.h gdb-0222/gdb/config/sparc/xm-xplynx.h
+gdb-0222/gdb/config/vax/xm-vaxult2.h gdb-0222/gdb/config/vax/xm-vaxut2.h
+gdb-0222/gdb/gdbtk/generic/gdbtk-varobj.c gdb-0222/gdb/gdbtk/generic/gdbtk-vobj.c
+gdb-0222/gdb/osf-share/cma_stack_int.h gdb-0222/gdb/osf-share/cma_stkint.h
+gdb-0222/gdb/testsuite/gdb.base/coremaker2.c gdb-0222/gdb/testsuite/gdb.base/core2maker.c
+gdb-0222/gdb/tui/tuiSourceWin.c gdb-0222/gdb/tui/tuiWinSource.c
+gdb-0222/gdb/tui/tuiSourceWin.h gdb-0222/gdb/tui/tuiWinSource.h
+gdb-0222/bfd/ChangeLog-9193 gdb-0222/bfd/ChangeLog.9193
+gdb-0222/bfd/ChangeLog-9495 gdb-0222/bfd/ChangeLog.9495
+gdb-0222/bfd/ChangeLog-9697 gdb-0222/bfd/ChangeLog.9697
+gdb-0222/bfd/coff-tic80.c gdb-0222/bfd/coff-tc80.c
+gdb-0222/sim/mips/dv-tx3904irc.c gdb-0222/sim/mips/dv-tx3irc.c
+gdb-0222/sim/mips/dv-tx3904sio.c gdb-0222/sim/mips/dv-tx3sio.c
+gdb-0222/sim/mips/dv-tx3904tmr.c gdb-0222/sim/mips/dv-tx3tmr.c
+gdb-0222/sim/mn10300/dv-mn103int.c gdb-0222/sim/mn10300/dv-mn1int.c
+gdb-0222/sim/mn10300/dv-mn103iop.c gdb-0222/sim/mn10300/dv-mn1iop.c
+gdb-0222/sim/mn10300/dv-mn103ser.c gdb-0222/sim/mn10300/dv-mn1ser.c
+gdb-0222/sim/mn10300/dv-mn103tim.c gdb-0222/sim/mn10300/dv-mn1tim.c
+gdb-0222/sim/ppc/corefile-n.h gdb-0222/sim/ppc/corefle-n.h
+gdb-0222/sim/ppc/idecode_branch.h gdb-0222/sim/ppc/idec_branch.h
+gdb-0222/sim/ppc/idecode_expression.h gdb-0222/sim/ppc/idec_expression.h
+gdb-0222/sim/ppc/idecode_fields.h gdb-0222/sim/ppc/idec_fields.h
+gdb-0222/sim/ppc/sim-endian-n.h gdb-0222/sim/ppc/sim-endn.h
+gdb-0222/sim/testsuite/d10v-elf/t-ae-ld-d.s gdb-0222/sim/testsuite/d10v-elf/t-ld-d.s
+gdb-0222/sim/testsuite/d10v-elf/t-ae-ld-i.s gdb-0222/sim/testsuite/d10v-elf/t-ld-i.s
+gdb-0222/sim/testsuite/d10v-elf/t-ae-ld-id.s gdb-0222/sim/testsuite/d10v-elf/t-ld-id.s
+gdb-0222/sim/testsuite/d10v-elf/t-ae-ld-im.s gdb-0222/sim/testsuite/d10v-elf/t-ld-im.s
+gdb-0222/sim/testsuite/d10v-elf/t-ae-ld-ip.s gdb-0222/sim/testsuite/d10v-elf/t-ld-ip.s
+gdb-0222/sim/testsuite/d10v-elf/t-ae-ld2w-d.s gdb-0222/sim/testsuite/d10v-elf/t-ld2-d.s
+gdb-0222/sim/testsuite/d10v-elf/t-ae-ld2w-i.s gdb-0222/sim/testsuite/d10v-elf/t-ld2-i.s
+gdb-0222/sim/testsuite/d10v-elf/t-ae-ld2w-id.s gdb-0222/sim/testsuite/d10v-elf/t-ld2-id.s
+gdb-0222/sim/testsuite/d10v-elf/t-ae-ld2w-im.s gdb-0222/sim/testsuite/d10v-elf/t-ld2-im.s
+gdb-0222/sim/testsuite/d10v-elf/t-ae-ld2w-ip.s gdb-0222/sim/testsuite/d10v-elf/t-ld2-ip.s
+gdb-0222/sim/testsuite/d10v-elf/t-ae-st-d.s gdb-0222/sim/testsuite/d10v-elf/t-st-d.s
+gdb-0222/sim/testsuite/d10v-elf/t-ae-st-i.s gdb-0222/sim/testsuite/d10v-elf/t-st-i.s
+gdb-0222/sim/testsuite/d10v-elf/t-ae-st-id.s gdb-0222/sim/testsuite/d10v-elf/t-st-id.s
+gdb-0222/sim/testsuite/d10v-elf/t-ae-st-im.s gdb-0222/sim/testsuite/d10v-elf/t-st-im.s
+gdb-0222/sim/testsuite/d10v-elf/t-ae-st-ip.s gdb-0222/sim/testsuite/d10v-elf/t-st-ip.s
+gdb-0222/sim/testsuite/d10v-elf/t-ae-st-is.s gdb-0222/sim/testsuite/d10v-elf/t-st-is.s
+gdb-0222/sim/testsuite/d10v-elf/t-ae-st2w-d.s gdb-0222/sim/testsuite/d10v-elf/t-st2-d.s
+gdb-0222/sim/testsuite/d10v-elf/t-ae-st2w-i.s gdb-0222/sim/testsuite/d10v-elf/t-st2-i.s
+gdb-0222/sim/testsuite/d10v-elf/t-ae-st2w-id.s gdb-0222/sim/testsuite/d10v-elf/t-st2-id.s
+gdb-0222/sim/testsuite/d10v-elf/t-ae-st2w-im.s gdb-0222/sim/testsuite/d10v-elf/t-st2-im.s
+gdb-0222/sim/testsuite/d10v-elf/t-ae-st2w-ip.s gdb-0222/sim/testsuite/d10v-elf/t-st2-ip.s
+gdb-0222/sim/testsuite/d10v-elf/t-ae-st2w-is.s gdb-0222/sim/testsuite/d10v-elf/t-st2-is.s
+gdb-0222/sim/testsuite/d30v-elf/ls-ld4bhu.S gdb-0222/sim/testsuite/d30v-elf/ls-ld4bu.S
+gdb-0222/intl/po2tbl.sed.in gdb-0222/intl/po2tblsed.in
+gdb-0222/intl/intlh.inst.in gdb-0222/intl/intlh_inst.in
+gdb-0222/readline/config.h.in gdb-0222/readline/config.h-in
+gdb-0222/readline/config.h.bot gdb-0222/readline/config.h-bot
+gdb-0222/gdb/nindy-share/b.out.h gdb-0222/gdb/nindy-share/b_out.h
+gdb-0222/gdb/c-exp.tab.c gdb-0222/gdb/c-exp_tab.c
+gdb-0222/gdb/jv-exp.tab.c gdb-0222/gdb/jv-exp_tab.c
+gdb-0222/gdb/f-exp.tab.c gdb-0222/gdb/f-exp_tab.c
+gdb-0222/gdb/m2-exp.tab.c gdb-0222/gdb/m2-exp_tab.c
+gdb-0222/gdb/testsuite/gdb.c++ gdb-0222/gdb/testsuite/gdb.cxx
+gdb-0222/gdb/testsuite/gdb.c++/Makefile.in gdb-0222/gdb/testsuite/gdb.cxx/Makefile.in
+gdb-0222/gdb/testsuite/gdb.c++/ambiguous.cc gdb-0222/gdb/testsuite/gdb.cxx/ambiguous.cc
+gdb-0222/gdb/testsuite/gdb.c++/ambiguous.exp gdb-0222/gdb/testsuite/gdb.cxx/ambiguous.exp
+gdb-0222/gdb/testsuite/gdb.c++/annota2.cc gdb-0222/gdb/testsuite/gdb.cxx/annota2.cc
+gdb-0222/gdb/testsuite/gdb.c++/annota2.exp gdb-0222/gdb/testsuite/gdb.cxx/annota2.exp
+gdb-0222/gdb/testsuite/gdb.c++/anon-union.cc gdb-0222/gdb/testsuite/gdb.cxx/anon-union.cc
+gdb-0222/gdb/testsuite/gdb.c++/anon-union.exp gdb-0222/gdb/testsuite/gdb.cxx/anon-union.exp
+gdb-0222/gdb/testsuite/gdb.c++/classes.exp gdb-0222/gdb/testsuite/gdb.cxx/classes.exp
+gdb-0222/gdb/testsuite/gdb.c++/configure gdb-0222/gdb/testsuite/gdb.cxx/configure
+gdb-0222/gdb/testsuite/gdb.c++/configure.in gdb-0222/gdb/testsuite/gdb.cxx/configure.in
+gdb-0222/gdb/testsuite/gdb.c++/cplusfuncs.cc gdb-0222/gdb/testsuite/gdb.cxx/cplusfuncs.cc
+gdb-0222/gdb/testsuite/gdb.c++/cplusfuncs.exp gdb-0222/gdb/testsuite/gdb.cxx/cplusfuncs.exp
+gdb-0222/gdb/testsuite/gdb.c++/ctti.exp gdb-0222/gdb/testsuite/gdb.cxx/ctti.exp
+gdb-0222/gdb/testsuite/gdb.c++/cttiadd.cc gdb-0222/gdb/testsuite/gdb.cxx/cttiadd.cc
+gdb-0222/gdb/testsuite/gdb.c++/cttiadd1.cc gdb-0222/gdb/testsuite/gdb.cxx/cttiadd1.cc
+gdb-0222/gdb/testsuite/gdb.c++/cttiadd2.cc gdb-0222/gdb/testsuite/gdb.cxx/cttiadd2.cc
+gdb-0222/gdb/testsuite/gdb.c++/cttiadd3.cc gdb-0222/gdb/testsuite/gdb.cxx/cttiadd3.cc
+gdb-0222/gdb/testsuite/gdb.c++/demangle.exp gdb-0222/gdb/testsuite/gdb.cxx/demangle.exp
+gdb-0222/gdb/testsuite/gdb.c++/derivation.cc gdb-0222/gdb/testsuite/gdb.cxx/derivation.cc
+gdb-0222/gdb/testsuite/gdb.c++/derivation.exp gdb-0222/gdb/testsuite/gdb.cxx/derivation.exp
+gdb-0222/gdb/testsuite/gdb.c++/inherit.exp gdb-0222/gdb/testsuite/gdb.cxx/inherit.exp
+gdb-0222/gdb/testsuite/gdb.c++/local.cc gdb-0222/gdb/testsuite/gdb.cxx/local.cc
+gdb-0222/gdb/testsuite/gdb.c++/local.exp gdb-0222/gdb/testsuite/gdb.cxx/local.exp
+gdb-0222/gdb/testsuite/gdb.c++/member-ptr.cc gdb-0222/gdb/testsuite/gdb.cxx/member-ptr.cc
+gdb-0222/gdb/testsuite/gdb.c++/member-ptr.exp gdb-0222/gdb/testsuite/gdb.cxx/member-ptr.exp
+gdb-0222/gdb/testsuite/gdb.c++/method.cc gdb-0222/gdb/testsuite/gdb.cxx/method.cc
+gdb-0222/gdb/testsuite/gdb.c++/method.exp gdb-0222/gdb/testsuite/gdb.cxx/method.exp
+gdb-0222/gdb/testsuite/gdb.c++/misc.cc gdb-0222/gdb/testsuite/gdb.cxx/misc.cc
+gdb-0222/gdb/testsuite/gdb.c++/misc.exp gdb-0222/gdb/testsuite/gdb.cxx/misc.exp
+gdb-0222/gdb/testsuite/gdb.c++/overload.cc gdb-0222/gdb/testsuite/gdb.cxx/overload.cc
+gdb-0222/gdb/testsuite/gdb.c++/overload.exp gdb-0222/gdb/testsuite/gdb.cxx/overload.exp
+gdb-0222/gdb/testsuite/gdb.c++/ovldbreak.cc gdb-0222/gdb/testsuite/gdb.cxx/ovldbreak.cc
+gdb-0222/gdb/testsuite/gdb.c++/ovldbreak.exp gdb-0222/gdb/testsuite/gdb.cxx/ovldbreak.exp
+gdb-0222/gdb/testsuite/gdb.c++/ref-types.cc gdb-0222/gdb/testsuite/gdb.cxx/ref-types.cc
+gdb-0222/gdb/testsuite/gdb.c++/ref-types.exp gdb-0222/gdb/testsuite/gdb.cxx/ref-types.exp
+gdb-0222/gdb/testsuite/gdb.c++/templates.cc gdb-0222/gdb/testsuite/gdb.cxx/templates.cc
+gdb-0222/gdb/testsuite/gdb.c++/templates.exp gdb-0222/gdb/testsuite/gdb.cxx/templates.exp
+gdb-0222/gdb/testsuite/gdb.c++/userdef.cc gdb-0222/gdb/testsuite/gdb.cxx/userdef.cc
+gdb-0222/gdb/testsuite/gdb.c++/userdef.exp gdb-0222/gdb/testsuite/gdb.cxx/userdef.exp
+gdb-0222/gdb/testsuite/gdb.c++/virtfunc.cc gdb-0222/gdb/testsuite/gdb.cxx/virtfunc.cc
+gdb-0222/gdb/testsuite/gdb.c++/virtfunc.exp gdb-0222/gdb/testsuite/gdb.cxx/virtfunc.exp
+gdb-0222/gdb/testsuite/.gdbinit gdb-0222/gdb/testsuite/gdb.ini
+gdb-0222/sim/ppc/.gdbinit gdb-0222/sim/ppc/gdb.ini
--- /dev/null	Sat Mar 18 17:07:20 2000
+++ gdb/config/djgpp/djcheck.sh	Sat Mar 18 15:44:22 2000
@@ -0,0 +1,32 @@
+#!/bin/sh
+
+# A shell script to run the test suite on the DJGPP version of GDB.
+
+ORIGDIR=`pwd`
+GDB=${ORIGDIR}/../gdb.exe
+SUBDIRS=`find $ORIGDIR -type d ! -ipath $ORIGDIR`
+
+for d in $SUBDIRS
+do
+  cd $d
+  echo "Running tests in $d..."
+  for f in *.out
+  do
+    test -f $f || break
+    base=`basename $f .out`
+    if test "${base}" = "dbx" ; then
+	options=-dbx
+    else
+	options=
+    fi
+    $GDB ${options} < ${base}.in 2>&1 \
+      | sed -e '/^GNU gdb /s/ [.0-9][.0-9]*//' \
+            -e '/Starting program: /s|[A-z]:/.*/||' \
+            -e '/main (.*argv=/s/\(argv\|envp\)=0x[0-9a-f][0-9a-f]*/\1=XYZ/g' \
+      > ${base}.tst
+    if diff --binary -u ${base}.out ${base}.tst ; then
+      rm -f ${base}.tst
+    fi
+  done
+done
+
From kettenis@wins.uva.nl Sat Apr 01 00:00:00 2000
From: Mark Kettenis <kettenis@wins.uva.nl>
To: tromey@cygnus.com
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: patch for gdb.texinfo
Date: Sat, 01 Apr 2000 00:00:00 -0000
Message-id: <200002010109.e1119Aw07492@delius.kettenis.local>
References: <200001281642.TAA04176@netserv1.chg.ru> <3891CD13.A68984BA@shebs.cnchost.com> <879017usuu.fsf@cygnus.com>
X-SW-Source: 2000-q1/msg00062.html
Content-length: 699

   From: Tom Tromey <tromey@cygnus.com>
   Date: 30 Jan 2000 14:55:53 -0700

   Stan> Certainly many GDB users would be disappointed if we trashed
   Stan> Linux support for any kernel older than, say, 2.2.5!

   Is that the official target kernel?  I still run 2.0.34 (!) and an
   unpatched gdb doesn't work on my box.

Is that gdb-4.18 or the current CVS version?

I have been hacking on the Linux i386 native support file last week,
and I realized that since that file uses PTRACE_GETREGS, it won't work
on linux 2.0.x, and won't even compile on a libc5 system.  Looks like
support for these systems was sacrificed for the SSE register
support.

Are there any other problems you know of?

Mark