https://bugs.kde.org/show_bug.cgi?id=400593
--- Comment #2 from Petar Jovanovic <mips3...@gmail.com> --- I can see new failures with the change applied: == 238 tests, 4 stderr failures, 4 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == none/tests/bigcode (stdout) none/tests/bigcode (stderr) none/tests/map_unmap (stdout) none/tests/map_unmap (stderr) none/tests/sigstackgrowth (stdout) none/tests/sigstackgrowth (stderr) none/tests/stackgrowth (stdout) none/tests/stackgrowth (stderr) arch: x86_64 glibc version: 2.27 I am getting these kind of errors: +--18001:0: aspacem segment mismatch: V's seg 1st, kernel's 2nd: +--18001:0: aspacem 1: file 0000108000-0000108fff 4096 r-x-- SmFixed d=0x........ i=178667325 o=0 (1,64) /home/petarj/radni/valgrind/trunk/none/tests/sigstackgrowth +--18001:0: aspacem ...: .... 0000108000-0000108fff 4096 r-x.. ....... d=0x........ i=178667325 o=0 (.) m=. /home/petarj/radni/valgrind/trunk/none/tests/sigstackgrowth +--18001:0: aspacem sync check at m_aspacemgr/aspacemgr-linux.c:2053 (vgPlain_am_get_advisory): FAILED +--18001:0: aspacem +--18001:0: aspacem Valgrind: FATAL: aspacem assertion failed: +--18001:0: aspacem VG_(am_do_sync_check) (__PRETTY_FUNCTION__,__FILE__,__LINE__) +--18001:0: aspacem at m_aspacemgr/aspacemgr-linux.c:2053 (vgPlain_am_get_advisory) +--18001:0: aspacem Exiting now. According to the results on the valgrind-testresults mailing list, it seems these errors are already present on some arches and configurations. -- You are receiving this mail because: You are watching all bug changes.
