ctor_copy_dtor.cc still consuming outrageous amounts of memory

[Nix]

Despite Zack's plaint in October, it's still going bananas; 1Gb virtual
set size is a little over the top.

This patch seems to help but doesn't stop it. (I guess I haven't trapped
all the places where memory is disappearing in there. I'm not entirely
used to the standard string yet.

For now, I've entirely disabled test01, and it seems to work.)

diff -durN gcc/libstdc++-v3/testsuite/21_strings/ctor_copy_dtor.cc gcc-hacking/libstdc++-v3/testsuite/21_strings/ctor_copy_dtor.cc
--- gcc/libstdc++-v3/testsuite/21_strings/ctor_copy_dtor.cc	Fri Jan 26 21:14:35 2001
+++ gcc-hacking/libstdc++-v3/testsuite/21_strings/ctor_copy_dtor.cc	Fri Jan 26 21:15:03 2001
@@ -112,6 +112,9 @@
   VERIFY( str01 == str04 );
 
 
+#if 0
+  // XXX These tests have been temporarily disabled.
+  // http://gcc.gnu.org/ml/libstdc++/2000-10/msg00033.html
   // basic_string(size_type n, char c, const allocator& a = allocator())
   csz01 = str01.max_size();
   try {
@@ -149,7 +152,7 @@
   catch(...) {
     VERIFY( false );
   }
-
+#endif
 
   // template<typename _InputIter>
   //   basic_string(_InputIter begin, _InputIter end, const allocator& a)

-- 
`Anyhow, that pipe dream doesn't say anything about the question you
 asked.  (I am planning for a career in politics.)' --- Mark Mitchell
                                                      on the GCC list