mirrors/gcc
0
0
Fork 0
mirror of https://gcc.gnu.org/git/gcc.git synced 2024-11-30 07:14:09 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

index.html: Explain memory "leaks" due to allocators.

Browse Source 
2003-03-12  Jonathan Wakely  <redi@gcc.gnu.org>

	* docs/html/faq/index.html: Explain memory "leaks" due to allocators.
	* docs/html/faq/index.txt: Regenerate.
	* docs/html/debug.html: Add a bit to allocator text and fix XHTML.

From-SVN: r64273
This commit is contained in:
Jonathan Wakely 2003-03-13 00:15:59 +00:00
parent 03d0dce160
commit 408e31a2dd
4 changed files with 184 additions and 150 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
libstdc++-v3/ChangeLog
View File

@ -1,3 +1,9 @@
2003-03-12 Jonathan Wakely <redi@gcc.gnu.org>
* docs/html/faq/index.html: Explain memory "leaks" due to allocators.
* docs/html/faq/index.txt: Regenerate.
* docs/html/debug.html: Add a bit to allocator text and fix XHTML.
2003-03-12 Andreas Schwab <schwab@suse.de>
* acinclude.m4 (GLIBCPP_EXPORT_INSTALL_INFO): Avoid trailing /. in

52
libstdc++-v3/docs/html/debug.html
View File

@ -17,13 +17,13 @@
<h1 class="centered"><a name="top">Debugging schemes and strategies</a></h1>
<p class="fineprint"><em>
<p>The latest version of this document is always available at
The latest version of this document is always available at
<a href="http://gcc.gnu.org/onlinedocs/libstdc++/debug.html">
http://gcc.gnu.org/onlinedocs/libstdc++/debug.html</a>.
</p>
</em></p>
<p>To the <a href="http://gcc.gnu.org/libstdc++/">libstdc++-v3 homepage</a>.
</p>
<p><em>
To the <a href="http://gcc.gnu.org/libstdc++/">libstdc++-v3 homepage</a>.
</em></p>
<!-- ####################################################### -->
@ -34,7 +34,7 @@
code with GNU tools.
</p>
<h3 class="left"><a name="g++">Compiler flags determine debug info</a></h3>
<h3 class="left"><a name="gplusplus">Compiler flags determine debug info</a></h3>
<p>The default optimizations and debug flags for a libstdc++ build are
<code>-g -O2</code>. However, both debug and optimization flags can
be varied to change debugging characteristics. For instance,
@ -52,7 +52,7 @@
</p>
<p>Many other options are available: please see
<a href=http://gcc.gnu.org/onlinedocs/gcc/Debugging-Options.html#Debugging%20Options> "Options for Debugging Your Program" </a>
<a href="http://gcc.gnu.org/onlinedocs/gcc/Debugging-Options.html#Debugging%20Options">"Options for Debugging Your Program"</a>
in Using the GNU Compiler Collection (GCC) for a complete list.
</p>
@ -60,30 +60,31 @@
<h3 class="left"><a name="lib">Using special flags to make a debug binary</a></h3>
<p>There are two ways to build libstdc++ with debug flags. The first
is to run make from the toplevel in a freshly-configured tree with
specialized debug <code>CXXFLAGS</code>, as in <dd> <code> make
CXXFLAGS='-g3 -O0' all </code></dd>
specialized debug <code>CXXFLAGS</code>, as in
</p>
<pre>
make CXXFLAGS='-g3 -O0' all
</pre>
<p>This quick and dirty approach is often sufficient for quick
debugging tasks, but the lack of state can be confusing in the long
term.
</p>
<p>A second approach is to use the configuration flags
</p>
<dd><code>--enable-debug</code></dd>
<pre>
--enable-debug
</pre>
<p>and perhaps</p>
<dd><code>--enable-debug-flags='...'</code></dd>
<pre>
--enable-debug-flags='...'
</pre>
<p>to create a separate debug build. Both the normal build and the
debug build will persist, without having to specify
<code>CXXFLAGS</code>, and the debug library will be installed in a
separate directory tree, in <code>(prefix)/lib/debug</code>. For
more information, look at the configuration options document
<a href=http://gcc.gnu.org/onlinedocs/libstdc++/configopts.html>here</a>
more information, look at the <a href="configopts.html">configuration
options</a> document.
</p>
@ -92,7 +93,7 @@
<p>There are various third party memory tracing and debug utilities
that can be used to provide detailed memory allocation information
about C++ code. An exhaustive list of tools is not going to be
attempted, but include <code>mtrace</code>, <code>valgrind</code>,
attempted, but includes <code>mtrace</code>, <code>valgrind</code>,
<code>mudflap</code>, and <code>purify</code>. Also highly
recommended are <code>libcwd</code> and some other one that I
forget right now.
@ -103,14 +104,15 @@
that uses <code>new</code> and <code>delete</code>:
there are different kinds of allocation schemes that can be used by
<code> std::allocator </code>. For implementation details, see this
<a href=http://gcc.gnu.org/onlinedocs/libstdc++/ext/howto.html#3>
document </a> and look specifically for <code>GLIBCPP_FORCE_NEW</code>.
<a href="ext/howto.html#3"> document</a> and look specifically for
<code>GLIBCPP_FORCE_NEW</code>.
</p>
<p>In a nutshell, the default allocator used by <code>
std::allocator</code> is a high-performance pool allocator, and can
give the mistaken impression that memory is being leaked, when in
reality the memory is reclaimed after program termination.
reality the memory is still being used by the library and is reclaimed
after program termination.
</p>
<p>For valgrind, there are some specific items to keep in mind. First
@ -164,15 +166,15 @@
<p>Suggested valgrind flags, given the suggestions above about setting
up the runtime environment, library, and test file, might be:
<dd><code>valgrind -v --num-callers=20 --leak-check=yes
--leak-resolution=high --show-reachable=yes a.out</code></dd>
</p>
<pre>
valgrind -v --num-callers=20 --leak-check=yes --leak-resolution=high --show-reachable=yes a.out
</pre>
<h3 class="left"><a name="gdb">Some gdb strategies</a></h3>
<p>Many options are available for gdb itself: please see <a
href=http://sources.redhat.com/gdb/current/onlinedocs/gdb_13.html#SEC109>
href="http://sources.redhat.com/gdb/current/onlinedocs/gdb_13.html#SEC109">
"GDB features for C++" </a> in the gdb documentation. Also
recommended: the other parts of this manual.
</p>

13
libstdc++-v3/docs/html/faq/index.html
View File

@ -94,6 +94,7 @@
<em>constraints</em> in the STL...</a> </li>
<li><a href="#4_4_dlsym">program crashes when using library code
in a dynamically-loaded library</a> </li>
<li><a href="#4_4_leak">"memory leaks" in containers</a> </li>
</ul>
</li>
<li><a href="#4_5">Aw, that's easy to fix!</a> </li>
@ -795,6 +796,18 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
// link the executable
g++ -fPIC -rdynamic -o foo ... -L. -lfoo -ldl</pre>
<p><a name="4_4_leak"><strong>"memory leaks" in containers</strong></a>
A few people have reported that the standard containers appear
to leak memory when tested with memory checkers such as
<a href="http://developer.kde.org/~sewardj/">valgrind</a>.
The library's default allocators keep free memory in a pool
for later reuse, rather than returning it to the OS. Although
this memory is always reachable by the library and is never
lost, memory debugging tools can report it as a leak. If you
want to test the library for memory leaks please read
<a href="../debug.html#mem">Tips for memory leak hunting</a>
first.
</p>
<hr />
<h2><a name="4_5">4.5 Aw, that's easy to fix!</a></h2>

263
libstdc++-v3/docs/html/faq/index.txt
View File

@ -51,17 +51,18 @@
o [40]errors about *Concept and constraints in the STL...
o [41]program crashes when using library code in a
dynamically-loaded library
5. [42]Aw, that's easy to fix!
5. [43]Miscellaneous
1. [44]string::iterator is not char*; vector<T>::iterator is not
o [42]"memory leaks" in containers
5. [43]Aw, that's easy to fix!
5. [44]Miscellaneous
1. [45]string::iterator is not char*; vector<T>::iterator is not
T*
2. [45]What's next after libstdc++-v3?
3. [46]What about the STL from SGI?
4. [47]Extensions and Backward Compatibility
5. [48][removed]
6. [49]Is libstdc++-v3 thread-safe?
7. [50]How do I get a copy of the ISO C++ Standard?
8. [51]What's an ABI and why is it so messy?
2. [46]What's next after libstdc++-v3?
3. [47]What about the STL from SGI?
4. [48]Extensions and Backward Compatibility
5. [49][removed]
6. [50]Is libstdc++-v3 thread-safe?
7. [51]How do I get a copy of the ISO C++ Standard?
8. [52]What's an ABI and why is it so messy?
_________________________________________________________________
1.0 General Information
@ -71,19 +72,19 @@
The GNU Standard C++ Library v3 is an ongoing project to implement the
ISO 14882 Standard C++ library as described in chapters 17 through 27
and annex D. As the library reaches stable plateaus, it is captured in
a snapshot and released. The latest release is [52]the fourteenth
a snapshot and released. The latest release is [53]the fourteenth
snapshot but newer versions have been included in recent GCC releases.
For those who want to see exactly how far the project has come, or
just want the latest bleeding-edge code, the up-to-date source is
available over anonymous CVS, and can even be browsed over the Web
(see [53]1.4 below).
(see [54]1.4 below).
The older libstdc++-v2 project is no longer maintained; the code has
been completely replaced and rewritten. [54]If you are using V2, then
been completely replaced and rewritten. [55]If you are using V2, then
you need to report bugs to your system vendor, not to the V3 list.
A more formal description of the V3 goals can be found in the official
[55]design document.
[56]design document.
_________________________________________________________________
1.2 Why should I use libstdc++?
@ -96,8 +97,8 @@
The GNU C/C++/FORTRAN/<pick-a-language> compiler (gcc, g++, etc) is
widely considered to be one of the leading compilers in the world. Its
development has recently been taken over by the [56]GCC team. All of
the rapid development and near-legendary [57]portability that are the
development has recently been taken over by the [57]GCC team. All of
the rapid development and near-legendary [58]portability that are the
hallmarks of an open-source project are being applied to libstdc++.
That means that all of the Standard classes and functions (such as
@ -115,16 +116,16 @@
Development and discussion is held on the libstdc++ mailing list.
Subscribing to the list, or searching the list archives, is open to
everyone. You can read instructions for doing so on the [58]homepage.
everyone. You can read instructions for doing so on the [59]homepage.
If you have questions, ideas, code, or are just curious, sign up!
_________________________________________________________________
1.4 How do I get libstdc++?
The fourteenth (and latest) snapshot of libstdc++-v3 is [59]available
The fourteenth (and latest) snapshot of libstdc++-v3 is [60]available
via ftp.
The [60]homepage has instructions for retrieving the latest CVS
The [61]homepage has instructions for retrieving the latest CVS
sources, and for browsing the CVS sources over the web.
The subset commonly known as the Standard Template Library (chapters
@ -140,7 +141,7 @@
1.6 How do I contribute to the effort?
Here is [61]a page devoted to this topic. Subscribing to the mailing
Here is [62]a page devoted to this topic. Subscribing to the mailing
list (see above, or the homepage) is a very good idea if you have
something to contribute, or if you have spare time and want to help.
Contributions don't have to be in the form of source code; anybody who
@ -175,11 +176,11 @@
extracted into an updated utilities library, but nobody has stated
such a project yet.
(The [62]Boost site houses free C++ libraries that do varying things,
(The [63]Boost site houses free C++ libraries that do varying things,
and happened to be started by members of the Standards Committee.
Certain "useful stuff" classes will probably migrate there.)
For the bold and/or desperate, the [63]GCC extensions page describes
For the bold and/or desperate, the [64]GCC extensions page describes
where to find the last libg++ source.
_________________________________________________________________
@ -189,16 +190,16 @@
remains unanswered, then just ask the mailing list. At present, you do
not need to be subscribed to the list to send a message to it. More
information is available on the homepage (including how to browse the
list archives); to send to the list, use [64]libstdc++@gcc.gnu.org.
list archives); to send to the list, use [65]libstdc++@gcc.gnu.org.
If you have a question that you think should be included here, or if
you have a question about a question/answer here, contact [65]Phil
Edwards or [66]Gabriel Dos Reis.
you have a question about a question/answer here, contact [66]Phil
Edwards or [67]Gabriel Dos Reis.
_________________________________________________________________
1.9 What are the license terms for libstdc++-v3?
See [67]our license description for these and related questions.
See [68]our license description for these and related questions.
_________________________________________________________________
2.0 Installation
@ -215,13 +216,13 @@
* The GNU Autotools are needed if you are messing with the configury
or makefiles.
The file [68]documentation.html provides a good overview of the steps
The file [69]documentation.html provides a good overview of the steps
necessary to build, install, and use the library. Instructions for
configuring the library with new flags such as --enable-threads are
there also, as well as patches and instructions for working with GCC
2.95.
The top-level install.html and [69]RELEASE-NOTES files contain the
The top-level install.html and [70]RELEASE-NOTES files contain the
exact build and installation instructions. You may wish to browse
those files over CVSweb ahead of time to get a feel for what's
required. RELEASE-NOTES is located in the ".../docs/17_intro/"
@ -238,8 +239,8 @@
The Concurrent Versions System is one of several revision control
packages. It was selected for GNU projects because it's free (speech),
free (beer), and very high quality. The [70]CVS entry in the GNU
software catalogue has a better description as well as a [71]link to
free (beer), and very high quality. The [71]CVS entry in the GNU
software catalogue has a better description as well as a [72]link to
the makers of CVS.
The "anonymous client checkout" feature of CVS is similar to anonymous
@ -290,7 +291,7 @@
people don't like it, so here are two pseudo-solutions:
If the only functions from libstdc++.a which you need are language
support functions (those listed in [72]clause 18 of the standard,
support functions (those listed in [73]clause 18 of the standard,
e.g., new and delete), then try linking against libsupc++.a (usually
specifying -lsupc++ when calling g++ for the final link step will do
it). This library contains only those support routines, one per object
@ -385,7 +386,7 @@
- < /dev/null" to display a list of predefined macros for any
particular installation.
This has been discussed on the mailing lists [73]quite a bit.
This has been discussed on the mailing lists [74]quite a bit.
This method is something of a wart. We'd like to find a cleaner
solution, but nobody yet has contributed the time.
@ -394,7 +395,7 @@
3.6 OS X ctype.h is broken! How can I hack it?
This is a long-standing bug in the OS X support. Fortunately, the
patch is quite simple, and well-known. [74]Here's a link to the
patch is quite simple, and well-known. [75]Here's a link to the
solution.
_________________________________________________________________
@ -432,7 +433,7 @@
enable itself.
You can fix the problems yourself, and learn more about the situation,
by reading [75]this short thread ("_GLIBCPP_USE_WCHAR_T undefined in
by reading [76]this short thread ("_GLIBCPP_USE_WCHAR_T undefined in
FreeBSD's c++config.h?").
_________________________________________________________________
@ -445,7 +446,7 @@
For 3.0.1, the most common "bug" is an apparently missing "../" in
include/Makefile, resulting in files like gthr.h and gthr-single.h not
being found. Please read [76]the configuration instructions for GCC,
being found. Please read [77]the configuration instructions for GCC,
specifically the part about configuring in a separate build directory,
and how strongly recommended it is. Building in the source directory
is fragile, is rarely tested, and tends to break, as in this case.
@ -453,7 +454,7 @@
For 3.1, the most common "bug" is a parse error when using <fstream>,
ending with a message, "bits/basic_file.h:52: parse error before `{'
token." Please read [77]the installation instructions for GCC,
token." Please read [78]the installation instructions for GCC,
specifically the part about not installing newer versions on top of
older versions. If you install 3.1 over a 3.0.x release, then the
wrong basic_file.h header will be found (its location changed between
@ -522,30 +523,30 @@ New:
libstdc++. If you are experiencing one of these problems, you can find
more information on the libstdc++ and the GCC mailing lists.
Before reporting a bug, examine the [78]bugs database with the
Before reporting a bug, examine the [79]bugs database with the
category set to "libstdc++". The BUGS file in the source tree also
tracks known serious problems.
* Debugging is problematic, due to bugs in line-number generation
(mostly fixed in the compiler) and gdb lagging behind the compiler
(lack of personnel). We recommend configuring the compiler using
--with-dwarf2 if the DWARF2 debugging format is not already the
default on your platform. Also, [79]changing your GDB settings can
default on your platform. Also, [80]changing your GDB settings can
have a profound effect on your C++ debugging experiences. :-)
_________________________________________________________________
4.3 Bugs in the C++ language/lib specification
Yes, unfortunately, there are some. In a [80]message to the list,
Yes, unfortunately, there are some. In a [81]message to the list,
Nathan Myers announced that he has started a list of problems in the
ISO C++ Standard itself, especially with regard to the chapters that
concern the library. The list itself is [81]posted on his website.
concern the library. The list itself is [82]posted on his website.
Developers who are having problems interpreting the Standard may wish
to consult his notes.
For those people who are not part of the ISO Library Group (i.e.,
nearly all of us needing to read this page in the first place :-), a
public list of the library defects is occasionally published [82]here.
Some of these have resulted in [83]code changes.
public list of the library defects is occasionally published [83]here.
Some of these have resulted in [84]code changes.
_________________________________________________________________
4.4 Things in libstdc++ that only look like bugs
@ -577,7 +578,7 @@ New:
state on the previous file. The reason is that the state flags are not
cleared on a successful call to open(). The standard unfortunately did
not specify behavior in this case, and to everybody's great sorrow,
the [84]proposed LWG resolution (see DR #22) is to leave the flags
the [85]proposed LWG resolution (see DR #22) is to leave the flags
unchanged. You must insert a call to fs.clear() between the calls to
close() and open(), and then everything will work like we all expect
it to work.
@ -587,7 +588,7 @@ New:
same namespace as other comparison functions (e.g., 'using' them and
the <iterator> header), then you will suddenly be faced with huge
numbers of ambiguity errors. This was discussed on the -v3 list;
Nathan Myers [85]sums things up here. The collisions with
Nathan Myers [86]sums things up here. The collisions with
vector/string iterator types have been fixed for 3.1.
The g++-3 headers are not ours
@ -595,7 +596,7 @@ New:
If you have found an extremely broken header file which is causing
problems for you, look carefully before submitting a "high" priority
bug report (which you probably shouldn't do anyhow; see the last
paragraph of the page describing [86]the GCC bug database).
paragraph of the page describing [87]the GCC bug database).
If the headers are in ${prefix}/include/g++-3, or if the installed
library's name looks like libstdc++-2.10.a or libstdc++-libc6-2.10.so,
@ -620,7 +621,7 @@ type has changed in glibc 2.2. The patch is at
http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
Note that 2.95.x shipped with the [87]old v2 library which is no
Note that 2.95.x shipped with the [88]old v2 library which is no
longer maintained. Also note that gcc 2.95.3 fixes this problem, but
requires a separate patch for libstdc++-v3.
@ -633,7 +634,7 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
visibility, or you just plain forgot, etc).
More information, including how to optionally enable/disable the
checks, is available [88]here.
checks, is available [89]here.
dlopen/dlsym If you are using the C++ library across
dynamically-loaded objects, make certain that you are passing the
@ -649,22 +650,31 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
// link the executable
g++ -fPIC -rdynamic -o foo ... -L. -lfoo -ldl
"memory leaks" in containers A few people have reported that the
standard containers appear to leak memory when tested with memory
checkers such as [90]valgrind. The library's default allocators keep
free memory in a pool for later reuse, rather than returning it to the
OS. Although this memory is always reachable by the library and is
never lost, memory debugging tools can report it as a leak. If you
want to test the library for memory leaks please read [91]Tips for
memory leak hunting first.
_________________________________________________________________
4.5 Aw, that's easy to fix!
If you have found a bug in the library and you think you have a
working fix, then send it in! The main GCC site has a page on
[89]submitting patches that covers the procedure, but for libstdc++
[92]submitting patches that covers the procedure, but for libstdc++
you should also send the patch to our mailing list in addition to the
GCC patches mailing list. The libstdc++ [90]contributors' page also
GCC patches mailing list. The libstdc++ [93]contributors' page also
talks about how to submit patches.
In addition to the description, the patch, and the ChangeLog entry, it
is a Good Thing if you can additionally create a small test program to
test for the presence of the bug that your patch fixes. Bugs have a
way of being reintroduced; if an old bug creeps back in, it will be
caught immediately by the [91]testsuite -- but only if such a test
caught immediately by the [94]testsuite -- but only if such a test
exists.
_________________________________________________________________
@ -698,7 +708,7 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
libstdc++. Some of that is already happening, see 4.2. Some of
those changes are being predicted by the library maintainers, and
we add code to the library based on what the current proposed
resolution specifies. Those additions are listed in [92]the
resolution specifies. Those additions are listed in [95]the
extensions page.
2. Performance tuning. Lots of performance tuning. This too is
already underway for post-3.0 releases, starting with memory
@ -714,13 +724,13 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
type from C99.) Bugfixes and rewrites (to improve or fix thread
safety, for instance) will of course be a continuing task.
[93]This question about the next libstdc++ prompted some brief but
interesting [94]speculation.
[96]This question about the next libstdc++ prompted some brief but
interesting [97]speculation.
_________________________________________________________________
5.3 What about the STL from SGI?
The [95]STL from SGI, version 3.3, was the most recent merge of the
The [98]STL from SGI, version 3.3, was the most recent merge of the
STL codebase. The code in libstdc++ contains many fixes and changes,
and it is very likely that the SGI code is no longer under active
development. We expect that no future merges will take place.
@ -769,7 +779,7 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
This is a bit cleaner than defining typedefs for all the
instantiations you might need.
Extensions to the library have [96]their own page.
Extensions to the library have [99]their own page.
_________________________________________________________________
5.5 [removed]
@ -818,8 +828,8 @@ a
otherwise documented as safe, do not assume that two threads may
access a shared standard library object at the same time.
See chapters [97]17 (library introduction), [98]23 (containers), and
[99]27 (I/O) for more information.
See chapters [100]17 (library introduction), [101]23 (containers), and
[102]27 (I/O) for more information.
_________________________________________________________________
5.7 How do I get a copy of the ISO C++ Standard?
@ -830,11 +840,11 @@ a
their two-meeting commitment for voting rights, may get a copy of the
standard from their respective national standards organization. In the
USA, this national standards organization is ANSI and their website is
right [100]here. (And if you've already registered with them, clicking
right [103]here. (And if you've already registered with them, clicking
this link will take you to directly to the place where you can
[101]buy the standard on-line.
[104]buy the standard on-line.
Who is your country's member body? Visit the [102]ISO homepage and
Who is your country's member body? Visit the [105]ISO homepage and
find out!
_________________________________________________________________
@ -885,8 +895,8 @@ a
encompasses the standard library.
_________________________________________________________________
See [103]license.html for copying conditions. Comments and suggestions
are welcome, and may be sent to [104]the libstdc++ mailing list.
See [106]license.html for copying conditions. Comments and suggestions
are welcome, and may be sent to [107]the libstdc++ mailing list.
References
@ -931,66 +941,69 @@ References
39. ../faq/index.html#4_4_glibc
40. ../faq/index.html#4_4_checks
41. ../faq/index.html#4_4_dlsym
42. ../faq/index.html#4_5
43. ../faq/index.html#5_0
44. ../faq/index.html#5_1
45. ../faq/index.html#5_2
46. ../faq/index.html#5_3
47. ../faq/index.html#5_4
48. ../faq/index.html#5_5
49. ../faq/index.html#5_6
50. ../faq/index.html#5_7
51. ../faq/index.html#5_8
52. http://gcc.gnu.org/libstdc++/index.html#download
53. ../faq/index.html#1_4
54. ../faq/index.html#4_4_interface
55. ../17_intro/DESIGN
56. http://gcc.gnu.org/
57. http://gcc.gnu.org/gcc-3.0/buildstat.html
58. http://gcc.gnu.org/libstdc++/
59. http://gcc.gnu.org/libstdc++/index.html#download
60. http://gcc.gnu.org/libstdc++/
61. ../17_intro/contribute.html
62. http://www.boost.org/
63. http://gcc.gnu.org/extensions.html
64. mailto:libstdc++@gcc.gnu.org
65. mailto:pme@gcc.gnu.org
66. mailto:gdr@gcc.gnu.org
67. ../17_intro/license.html
68. ../documentation.html
69. ../17_intro/RELEASE-NOTES
70. http://www.gnu.org/software/cvs/cvs.html
71. http://www.cvshome.org/
72. ../18_support/howto.html
73. http://gcc.gnu.org/cgi-bin/htsearch?method=and&format=builtin-long&sort=score&words=_XOPEN_SOURCE+Solaris
74. http://gcc.gnu.org/ml/gcc/2002-03/msg00817.html
75. http://gcc.gnu.org/ml/libstdc++/2003-02/subjects.html#00286
76. http://gcc.gnu.org/install/configure.html
77. http://gcc.gnu.org/install/
78. http://gcc.gnu.org/bugs.html
79. http://gcc.gnu.org/ml/libstdc++/2002-02/msg00034.html
80. http://gcc.gnu.org/ml/libstdc++/1998/msg00006.html
81. http://www.cantrip.org/draft-bugs.txt
82. http://anubis.dkuug.dk/jtc1/sc22/wg21/
83. ../faq/index.html#5_2
84. ../ext/howto.html#5
85. http://gcc.gnu.org/ml/libstdc++/2001-01/msg00247.html
86. http://gcc.gnu.org/gnatswrite.html
87. ../faq/index.html#4_4_interface
88. ../19_diagnostics/howto.html#3
89. http://gcc.gnu.org/contribute.html
90. ../17_intro/contribute.html
91. ../faq/index.html#2_4
92. ../ext/howto.html#5
93. http://gcc.gnu.org/ml/libstdc++/1999/msg00080.html
94. http://gcc.gnu.org/ml/libstdc++/1999/msg00084.html
95. http://www.sgi.com/Technology/STL/
96. ../ext/howto.html
97. ../17_intro/howto.html#3
98. ../23_containers/howto.html#3
99. ../27_io/howto.html#9
100. http://www.ansi.org/
101. http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%2D1998
102. http://www.iso.ch/
103. ../17_intro/license.html
104. mailto:libstdc++@gcc.gnu.org
42. ../faq/index.html#4_4_leak
43. ../faq/index.html#4_5
44. ../faq/index.html#5_0
45. ../faq/index.html#5_1
46. ../faq/index.html#5_2
47. ../faq/index.html#5_3
48. ../faq/index.html#5_4
49. ../faq/index.html#5_5
50. ../faq/index.html#5_6
51. ../faq/index.html#5_7
52. ../faq/index.html#5_8
53. http://gcc.gnu.org/libstdc++/index.html#download
54. ../faq/index.html#1_4
55. ../faq/index.html#4_4_interface
56. ../17_intro/DESIGN
57. http://gcc.gnu.org/
58. http://gcc.gnu.org/gcc-3.0/buildstat.html
59. http://gcc.gnu.org/libstdc++/
60. http://gcc.gnu.org/libstdc++/index.html#download
61. http://gcc.gnu.org/libstdc++/
62. ../17_intro/contribute.html
63. http://www.boost.org/
64. http://gcc.gnu.org/extensions.html
65. mailto:libstdc++@gcc.gnu.org
66. mailto:pme@gcc.gnu.org
67. mailto:gdr@gcc.gnu.org
68. ../17_intro/license.html
69. ../documentation.html
70. ../17_intro/RELEASE-NOTES
71. http://www.gnu.org/software/cvs/cvs.html
72. http://www.cvshome.org/
73. ../18_support/howto.html
74. http://gcc.gnu.org/cgi-bin/htsearch?method=and&format=builtin-long&sort=score&words=_XOPEN_SOURCE+Solaris
75. http://gcc.gnu.org/ml/gcc/2002-03/msg00817.html
76. http://gcc.gnu.org/ml/libstdc++/2003-02/subjects.html#00286
77. http://gcc.gnu.org/install/configure.html
78. http://gcc.gnu.org/install/
79. http://gcc.gnu.org/bugs.html
80. http://gcc.gnu.org/ml/libstdc++/2002-02/msg00034.html
81. http://gcc.gnu.org/ml/libstdc++/1998/msg00006.html
82. http://www.cantrip.org/draft-bugs.txt
83. http://anubis.dkuug.dk/jtc1/sc22/wg21/
84. ../faq/index.html#5_2
85. ../ext/howto.html#5
86. http://gcc.gnu.org/ml/libstdc++/2001-01/msg00247.html
87. http://gcc.gnu.org/gnatswrite.html
88. ../faq/index.html#4_4_interface
89. ../19_diagnostics/howto.html#3
90. http://developer.kde.org/~sewardj/
91. ../debug.html#mem
92. http://gcc.gnu.org/contribute.html
93. ../17_intro/contribute.html
94. ../faq/index.html#2_4
95. ../ext/howto.html#5
96. http://gcc.gnu.org/ml/libstdc++/1999/msg00080.html
97. http://gcc.gnu.org/ml/libstdc++/1999/msg00084.html
98. http://www.sgi.com/Technology/STL/
99. ../ext/howto.html
100. ../17_intro/howto.html#3
101. ../23_containers/howto.html#3
102. ../27_io/howto.html#9
103. http://www.ansi.org/
104. http://webstore.ansi.org/ansidocstore/product.asp?sku=ISO%2FIEC+14882%2D1998
105. http://www.iso.ch/
106. ../17_intro/license.html
107. mailto:libstdc++@gcc.gnu.org