Imported Upstream version 1.64.0

[platform/upstream/boost.git] / libs / test / doc / html / boost / debug / break_memory_alloc.html

diff --git a/libs/test/doc/html/boost/debug/break_memory_alloc.html b/libs/test/doc/html/boost/debug/break_memory_alloc.html
index 68e3594..7fefea5 100644 (file)
--- a/libs/test/doc/html/boost/debug/break_memory_alloc.html
+++ b/libs/test/doc/html/boost/debug/break_memory_alloc.html
@@ -34,7 +34,7 @@
 </span>
 <span class="keyword">void</span> <span class="identifier">break_memory_alloc</span><span class="special">(</span><span class="keyword">long</span> mem_alloc_order_num<span class="special">)</span><span class="special">;</span></pre></div>
 <div class="refsect1">
-<a name="idp116072016"></a><h2>Description</h2>
+<a name="idp127033504"></a><h2>Description</h2>
 <p>On some platforms/memory managers (at the moment only on Windows/Visual Studio) one can tell a C Runtime to break on specific memory allocation. This can be used in combination with memory leak detection (which reports leaked memory allocation number) to locate the place where leak initiated. 
 </p>
 <div class="variablelist"><table border="0" class="variablelist compact">