From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 1059) id 10EA1393C89D; Thu, 11 Jun 2020 13:01:14 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 10EA1393C89D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1591880474; bh=TqCVYyWPDLekBESBwd8kP9RlCEYv2GdWU6N0MPUC7Hg=; h=From:To:Subject:Date:From; b=WmG/KPbI4tIQgYc3Gh5qKj69US62Z52MpOtN3UqjOqcJms3YNSqzzsUKOaf77nwXH vWRFxUGAJJz5QZ2Kq5u8MZrHtOd8QRQFRnjbHCZcdKHFzwjuzkJORVex5C8WB/y/xE +IpyjEWVibnJIoeBHfayheNtfL8/vvnAlFfVBrkU= Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Nathan Sidwell To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc/devel/c++-modules] libstdc++: Update/streamline Valgrind references X-Act-Checkin: gcc X-Git-Author: Gerald Pfeifer X-Git-Refname: refs/heads/devel/c++-modules X-Git-Oldrev: ff7da2b5d621d0aaf4a467344d0621eefd4aa78f X-Git-Newrev: e41b988cc5af34e9c1a3d37b717fbfcc52d7ff90 Message-Id: <20200611130114.10EA1393C89D@sourceware.org> Date: Thu, 11 Jun 2020 13:01:14 +0000 (GMT) X-BeenThere: libstdc++-cvs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libstdc++-cvs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jun 2020 13:01:14 -0000 https://gcc.gnu.org/g:e41b988cc5af34e9c1a3d37b717fbfcc52d7ff90 commit e41b988cc5af34e9c1a3d37b717fbfcc52d7ff90 Author: Gerald Pfeifer Date: Mon Jun 1 17:03:51 2020 +0200 libstdc++: Update/streamline Valgrind references * doc/xml/faq.xml: Adjust Valgrind reference and remove another. * doc/html/faq.html: Regenerate. Diff: --- libstdc++-v3/doc/html/faq.html | 4 ++-- libstdc++-v3/doc/xml/faq.xml | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/libstdc++-v3/doc/html/faq.html b/libstdc++-v3/doc/html/faq.html index 18407225d7a..967e5f5f348 100644 --- a/libstdc++-v3/doc/html/faq.html +++ b/libstdc++-v3/doc/html/faq.html @@ -700,7 +700,7 @@ of a few dozen kilobytes on startup. This pool is used to ensure it's possible to throw exceptions (such as bad_alloc) even when malloc is unable to allocate any more memory. - With some versions of valgrind + With some versions of valgrind this pool will be shown as "still reachable" when the process exits, e.g. still reachable: 72,704 bytes in 1 blocks. This memory is not a leak, because it's still in use by libstdc++, @@ -710,7 +710,7 @@

In the past, a few people reported that the standard containers appear to leak memory when tested with memory checkers such as - valgrind. + valgrind. Under some (non-default) configurations the library's allocators keep free memory in a pool for later reuse, rather than deallocating it with delete diff --git a/libstdc++-v3/doc/xml/faq.xml b/libstdc++-v3/doc/xml/faq.xml index cf8684e1cea..e419d3c22a0 100644 --- a/libstdc++-v3/doc/xml/faq.xml +++ b/libstdc++-v3/doc/xml/faq.xml @@ -993,7 +993,7 @@ of a few dozen kilobytes on startup. This pool is used to ensure it's possible to throw exceptions (such as bad_alloc) even when malloc is unable to allocate any more memory. - With some versions of valgrind + With some versions of valgrind this pool will be shown as "still reachable" when the process exits, e.g. still reachable: 72,704 bytes in 1 blocks. This memory is not a leak, because it's still in use by libstdc++, @@ -1004,7 +1004,7 @@ In the past, a few people reported that the standard containers appear to leak memory when tested with memory checkers such as - valgrind. + valgrind. Under some (non-default) configurations the library's allocators keep free memory in a pool for later reuse, rather than deallocating it with delete