Date: Sat, 14 May 2022 17:38:21 +0200 From: Paul Floyd <pjfloyd@wanadoo.fr> To: freebsd-toolchain@freebsd.org Subject: Re: clang options for load segments Message-ID: <43507d14-f691-46a9-f42c-eb43c2f8d0b5@wanadoo.fr> In-Reply-To: <4e2be84d-3929-6bb5-5bea-0444f29f429f@wanadoo.fr> References: <fb3e3660-a6c0-c8ce-5055-624cde7ce95c@wanadoo.fr> <4D81BCDE-ECBC-49D8-BF17-38E334141FE0@FreeBSD.org> <89794bb8-5e97-36a7-0b6a-fa2eaf76a72a@wanadoo.fr> <CAPyFy2BzBVX0Q1tB39CA-fXQj4b44MMVAhWOvi6fRaDPaEzs8g@mail.gmail.com> <4e2be84d-3929-6bb5-5bea-0444f29f429f@wanadoo.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/3/21 09:36, Paul Floyd wrote: > Hi Ed > > > > PT_LOAD, I'm fully in agreement, I need to fix this in Valgrind. > Over a year later, and this one is getting closer to being fixed. It was much harder than I anticipated to fix in Valgrind (mainly because of the hard coded assumption of a single RW PT_LOAD segment). https://bugs.kde.org/show_bug.cgi?id=452802 I'm planning for an update to devel/valgrind-devel as soon as possible. Not sure if it'll be in time for 13.1-RELEASE. A+ Paul
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43507d14-f691-46a9-f42c-eb43c2f8d0b5>