Date: Thu, 21 Sep 2023 07:28:44 +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-HWCVQnX1qW@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 #14 from Paul Floyd <pjfloyd@wanadoo.fr> --- There are 3 ways that Valgrind triggers reading debuginfo 1. from its own image as here 2. from the guest ld-elf.so.1 and exe which Valgrind loads 3. from anything that the guest loads once it is running under Valgrind. There's a longer explanation in coregrind/m_debuginfo/debuginfo.c starting = line 1028 The two main goals are to use the same code for all cases and to avoid loo= king for debuginfo in non executable files. I'm not sure if that second goal is still valid, but that's a different story. For case 1 (and 2) we can be absolutely certain that the file is an ELF executable. Case 1, the code wouldn't be running otherwise! I can probably bodge the code to make it look like a RW section was seen and just use the filename from the RX section. How have things changed between 13.2 and 14.0 to cause this? --=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-HWCVQnX1qW>