https://bugs.kde.org/show_bug.cgi?id=513533
--- Comment #4 from Paul Floyd <[email protected]> --- Most of the failures just needed more filtering. That leaves us with drd/tests/getaddrinfo with diffs like +Recursive locking not allowed: mutex 0x........, recursion count 1, owner 5. I don't want to default suppress that. It looks like there is some issue with mutexes being locked recursively. helgrind/tests/stackteardown fails with +!? New thread x starts with SP(0x........) unmapped That looks a bit iffy. With --sanity-level=3 ==23906== !? New thread 2 starts with SP(0x10057d000) unmapped --23906:0: aspacem segment mismatch: V's seg 1st, kernel's 2nd: --23906:0: aspacem 58: 7000724b6000-7000724b7fff 8192 ----- SmFixed d=0x000 i=0 o=0 (-1,-1) (none) --23906:0: aspacem ...: .... 7000724b6000-7000724b7fff 8192 rw-.. ....... d=0x000 i=30 o=0 (.) m=. /dev/macos/internals/[stack] --23906:0: aspacem sync check at m_aspacemgr/aspacemgr-linux.c:2485 (Bool vgPlain_am_notify_munmap(Addr, SizeT)): FAILED --23906:0: aspacem --23906:0: aspacem Valgrind: FATAL: aspacem assertion failed: --23906:0: aspacem VG_(am_do_sync_check) (__PRETTY_FUNCTION__,__FILE__,__LINE__) --23906:0: aspacem at m_aspacemgr/aspacemgr-linux.c:2485 (Bool vgPlain_am_notify_munmap(Addr, SizeT)) --23906:0: aspacem Exiting now. More than iffy. I'll probably push the code as-is and try to deal with these later. -- You are receiving this mail because: You are watching all bug changes.
