Author: philippe
Date: Sun May 22 21:48:09 2016
New Revision: 15880
Log:
Document brk segment limitation, reference manual in limit reached msg.
The msg telling brk cannot be extended confuses some users
so improve the documentation and have the msg referencing the doc.
Modified:
trunk/NEWS
trunk/coregrind/m_syswrap/syswrap-generic.c
trunk/docs/xml/manual-core.xml
trunk/memcheck/tests/linux/brk.stderr.exp
trunk/none/tests/linux/brk-overflow1.stderr.exp
trunk/none/tests/linux/brk-overflow2.stderr.exp
Modified: trunk/NEWS
==============================================================================
--- trunk/NEWS (original)
+++ trunk/NEWS Sun May 22 21:48:09 2016
@@ -107,6 +107,7 @@
n-i-bz massif --pages-as-heap=yes does not report peak caused by mmap+munmap
n-i-bz false positive leaks due to aspacemgr merging non heap segments with heap segments.
n-i-bz Fix ppoll_alarm exclusion on OS X
+n-i-bz Document brk segment limitation, reference manual in limit reached msg.
Release 3.11.0 (22 September 2015)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Modified: trunk/coregrind/m_syswrap/syswrap-generic.c
==============================================================================
--- trunk/coregrind/m_syswrap/syswrap-generic.c (original)
+++ trunk/coregrind/m_syswrap/syswrap-generic.c Sun May 22 21:48:09 2016
@@ -1324,6 +1324,7 @@
else
VG_(umsg)("Cannot map memory to grow brk segment in thread #%u "
"to %#lx\n", tid, newbrkP);
+ VG_(umsg)("(see section Limitations in user manual)\n");
goto bad;
}
Modified: trunk/docs/xml/manual-core.xml
==============================================================================
--- trunk/docs/xml/manual-core.xml (original)
+++ trunk/docs/xml/manual-core.xml Sun May 22 21:48:09 2016
@@ -2779,6 +2779,18 @@
<itemizedlist>
<listitem>
+ <para>Valgrind determines at startup the size of the 'brk segment'
+ using the RLIMIT_DATA rlim_cur, with a minimum of 1 MB and a
+ maximum of 8 MB. Valgrind outputs a message each time a program
+ tries to extend the brk segment beyond the size determined at
+ startup. Most programs will work properly with this limit,
+ typically by switching to the use of mmap to get more memory.
+ If your program really needs a big brk segment, you must change
+ the 8 MB hardcoded limit and recompile Valgrind.
+ </para>
+ </listitem>
+
+ <listitem>
<para>On x86 and amd64, there is no support for 3DNow!
instructions. If the translator encounters these, Valgrind will
generate a SIGILL when the instruction is executed. Apart from
Modified: trunk/memcheck/tests/linux/brk.stderr.exp
==============================================================================
--- trunk/memcheck/tests/linux/brk.stderr.exp (original)
+++ trunk/memcheck/tests/linux/brk.stderr.exp Sun May 22 21:48:09 2016
@@ -1,6 +1,8 @@
brk segment overflow in thread #1: can't grow to 0x........
+(see section Limitations in user manual)
brk segment overflow in thread #1: can't grow to 0x........
+(see section Limitations in user manual)
HEAP SUMMARY:
in use at exit: ... bytes in ... blocks
Modified: trunk/none/tests/linux/brk-overflow1.stderr.exp
==============================================================================
--- trunk/none/tests/linux/brk-overflow1.stderr.exp (original)
+++ trunk/none/tests/linux/brk-overflow1.stderr.exp Sun May 22 21:48:09 2016
@@ -1,3 +1,4 @@
brk segment overflow in thread #1: can't grow to 0x........
+(see section Limitations in user manual)
Modified: trunk/none/tests/linux/brk-overflow2.stderr.exp
==============================================================================
--- trunk/none/tests/linux/brk-overflow2.stderr.exp (original)
+++ trunk/none/tests/linux/brk-overflow2.stderr.exp Sun May 22 21:48:09 2016
@@ -1,5 +1,8 @@
brk segment overflow in thread #1: can't grow to 0x........
+(see section Limitations in user manual)
brk segment overflow in thread #1: can't grow to 0x........
+(see section Limitations in user manual)
brk segment overflow in thread #1: can't grow to 0x........
+(see section Limitations in user manual)
|