Critical ~__pool troubles (libstdc++/17937)

[Paolo Carlini]

Hi everyone,

earlier today (exactly while I was looking more into Carlo message)
Michael sent me this testcase, distilled from KDE arts:

#include <string>
#include <list>
using namespace std;
static list<string> modulePath;
int main()
{
  modulePath.push_back("hallo");
  return 0;
}

Therefore, no special settings are needed (e.g., per_type_pools) to
show that something is still not ok with ~__pool. I'm attaching below
valgrind's output for a --enable-__cxa_atexit build (removing it
avoids, as expected, all the errors).

Frankly, I'm wondering whether we really, *really*, /really/ need to
explicitly deallocate the pools instead of demanding the work to the
OS: why the original SGI/HP allocator didn't do that?? Perhaps Matt
could help here??

Thanks in advance,
Paolo.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: from_michael_valgrind_atexit
URL: <http://gcc.gnu.org/pipermail/libstdc++/attachments/20041011/a84db694/attachment.ksh>