I've added some tests to gdb.c++/m-static that correspond to the patch
in <http://sources.redhat.com/ml/gdb-patches/2002-08/msg00385.html>;
patches below.

A few tangential questions:

* I hope I got the stuff in brackets in the subject correct; is rfa
  "request for approval"?

* What's the convention for submitting new files (as opposed to
  patches to existing files)?  (I'd look through the mail archive for
  examples, but I don't seem to be able to access it right now.)  I'm
  attaching them below as files and hoping that the mailer will make
  it clear what they're named and so forth; please let me know if I
  should do anything else.

* CONTRIBUTE suggests using "cvs diff -cp", but everybody submits
  unidiff patches.  Should I change it to say "cvs diff -up"?

* Does "make clean" actually clean up the testsuite directory
  properly?  Looking at the Makefile in gdb.c++, it seems like it
  cleans up whatever's in the EXECUTABLES variable, which certainly
  doesn't include all the executables in that directory.  Is there
  something else magic going on, or should I audit the Makefile.in's
  in the various directories to see if they clean up everything?
  (Yes, I know, I should really type "make clean" and see what it
  does, but I don't feel like rebuilding gdb if somebody can answer
  the question quickly.)

Thanks,
David Carlton
carlton@math.stanford.edu

2002-08-16  David Carlton  <carlton@math.stanford.edu>

	* gdb.c++/m-static.exp: Added test 4.
	* gdb.c++/m-static.cc: Ditto.
	* gdb.c++/m-static.h: New file.
	* gdb.c++/m-static1.cc: New file.