https://bugs.kde.org/show_bug.cgi?id=486662
Bug ID: 486662
Summary: Running with --sanity-level=3 or higher fails on Linux
using btrfs
Classification: Developer tools
Product: valgrind
Version: 3.23 GIT
Platform: Other
OS: Other
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: pjfl...@wanadoo.fr
Target Milestone: ---
When running with --sanity-level=3 or higher the following assert gets
triggered
-361664:0: aspacem segment mismatch: V's seg 1st, kernel's 2nd:
--361664:0: aspacem 1: file 0000400000-0000400fff 4096 r----
SmFixed d=0x027 i=1025160 o=0
(1,67) /home/paulf/scratch/valgrind/none/tests/stackgrowth
--361664:0: aspacem ...: .... 0000400000-0000400fff 4096 r--..
....... d=0x01e i=1025160 o=0
(.) m=. /home/paulf/scratch/valgrind/none/tests/stackgrowth
--361664:0: aspacem sync check at m_aspacemgr/aspacemgr-linux.c:2147
(vgPlain_am_get_advisory): FAILE
D
--361664:0: aspacem
--361664:0: aspacem Valgrind: FATAL: aspacem assertion failed:
--361664:0: aspacem VG_(am_do_sync_check)
(__PRETTY_FUNCTION__,__FILE__,__LINE__)
--361664:0: aspacem at m_aspacemgr/aspacemgr-linux.c:2147
(vgPlain_am_get_advisory)
--361664:0: aspacem Exiting now.
This is early on in the process, when Valgrind is loading the guest exe. I can
reproduce the problem with any exe.
It seems like the values for the filesytem device are from /proc/self/maps and
the statx syscall are different. On my system I'm seeing vlaues of 30 and 32.
--
You are receiving this mail because:
You are watching all bug changes.
