https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273956
--- Comment #13 from Ed Maste <ema...@freebsd.org> ---
(In reply to Konstantin Belousov from comment #12)
The issue is just in Valgrind's assumptions of what the mappings will be.
I spotted this comment in its src:
/* A segment in the initial /proc/self/maps is considered a FileV
segment if either it has a file name associated with it or both its
device and inode numbers are != 0. See bug #124528. */
(It references /proc/self/maps from its Linux origins, but provides a sysctl
implementation on FreeBSD)
Also this comment:
If there is no RX or no RW mapping then we will not attempt to
read debuginfo for the file.
I think all of this logic is an attempt to determine if maps are part of
valgrind itself or the target process.
If allow_SkFileV is True, it will try load debug info if the
mapping at 'a' belongs to Valgrind; whereas normally (False)
it will not do that. This allows us to carefully control when
the thing will read symbols from the Valgrind executable itself.
--
You are receiving this mail because:
You are the assignee for the bug.
