From: Mark Wielaard Date: Thu, 11 Apr 2019 16:06:34 +0000 (+0200) Subject: none/tests/amd64-linux/map_32bits.vgtest fails too easily X-Git-Tag: VALGRIND_3_15_0~3 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=535d2ff4f2f755faa8b1a9e467833eca455bd2d7;p=thirdparty%2Fvalgrind.git none/tests/amd64-linux/map_32bits.vgtest fails too easily On various systems none/tests/amd64-linux/map_32bits.vgtest fails with: first mmap: Cannot allocate memory. The problem is that the --aspace-minaddr is too tight. Newer glibc seem to mmap some memory and so even our first mmap with MMAP_32BIT will fail. The solution is to make a bit more memory < 2GB available. If there is 16MB available the test always seems to succeed without needing too many tries. The original 256K is too low. https://bugs.kde.org/show_bug.cgi?id=406422 --- diff --git a/NEWS b/NEWS index 7faba7e92d..bf7b3dd843 100644 --- a/NEWS +++ b/NEWS @@ -152,6 +152,7 @@ where XXXXXX is the bug number as listed below. 406355 mcsignopass, mcsigpass, mcbreak fail due to difference in gdb output 406357 gdbserver_tests fails because of gdb output change 406360 memcheck/tests/libstdc++.supp needs more supression variants +406422 none/tests/amd64-linux/map_32bits.vgtest fails too easily n-i-bz add syswrap for PTRACE_GET|SET_THREAD_AREA on amd64. n-i-bz Fix callgrind_annotate non deterministic order for equal total n-i-bz callgrind_annotate --threshold=100 does not print all functions. diff --git a/none/tests/amd64-linux/map_32bits.vgtest b/none/tests/amd64-linux/map_32bits.vgtest index 2b7f3a04a6..43011e3cd9 100644 --- a/none/tests/amd64-linux/map_32bits.vgtest +++ b/none/tests/amd64-linux/map_32bits.vgtest @@ -1,5 +1,5 @@ prog: map_32bits # take a big aspacemgr minaddr, to quickly reach the 2GB limit -vgopts: -q --aspace-minaddr=0x7ff60000 +vgopts: -q --aspace-minaddr=0x7f000000 stderr_filter: filter_stderr