Date: Thu, 21 Sep 2023 01:23:23 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 273956] KERN_PROC_VMMAP does not read all mapped files Message-ID: <bug-273956-227-E6FUIsTVIF@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-273956-227@https.bugs.freebsd.org/bugzilla/> References: <bug-273956-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D273956 --- Comment #13 from Ed Maste <emaste@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 !=3D 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. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-273956-227-E6FUIsTVIF>