|
From: Philippe W. <phi...@sk...> - 2025-11-19 14:58:08
|
I have cleaned up all the shared memory segments and manually relaunched mremap4. It now succeeds but leaves behind it the shared memory segment lingering. Same behaviour on debian. And effectively, at least mremap4.c does not cleanup the shared memory after usage. So, as you said, likely this test starts to fail due to some kernel limit or config reached. Encountered on this system as it has not been rebooted since 1570 days :) I will improve the tests to have the shared mem cleanup up Philippe On Wed, 2025-11-19 at 15:12 +0100, Philippe Waroquiers via valgrind-testresults wrote: > Thanks for the info, I will take a look > > Philippe > > On Mon, 2025-11-17 at 08:03 +0100, Paul Floyd wrote: > > > > > > > On 17 Nov 2025, at 06:53, Philippe Waroquiers via valgrind-testresults > > > <val...@li...> wrote: > > > > > > valgrind revision: valgrind-3.27.0.GIT-fafb6efd4b-20251116 > > > C compiler: gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44) > > > GDB: GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-120.el7 > > > Assembler: GNU assembler version 2.27-44.base.el7_9.1 > > > C library: GNU C Library (GNU libc) stable release version 2.17 > > > uname -mrs: Linux 3.10.0-1127.13.1.el7.ppc64le ppc64le > > > Vendor version: CentOS Linux 7 (AltArch) > > > > > > Nightly build on gcc112 ( \S, ppc64le ) > > > Started at 2025-11-17 03:00:06 UTC > > > Ended at 2025-11-17 05:53:50 UTC > > > Results unchanged from 24 hours ago > > > > > > Checking out Valgrind source tree ... done > > > Configuring valgrind ... done > > > Building valgrind ... done > > > Running regression tests ... failed > > > > > > Regression test results follow > > > > > > == 741 tests, 3 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB > > > failures, 0 post failures == > > > none/tests/linux/mremap4 (stderr) > > > none/tests/linux/mremap5 (stderr) > > > none/tests/linux/mremap6 (stderr) > > > > gcc112 has 4072 unattached shared memory segments > > > > ------ Shared Memory Segments -------- > > key shmid owner perms bytes nattch status > > 0x00000000 589824 philippe 600 409600 0 > > 0x00000000 32769 philippe 600 409600 0 > > 0x00000000 32770 philippe 600 409600 0 > > 0x00000000 32771 philippe 600 1048576 0 > > > > Maybe the machine is hitting a limit there? > > > > A+ > > Paul > > > > > _______________________________________________ > valgrind-testresults mailing list > val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-testresults |