Date: Tue, 2 Mar 2021 17:55:37 -0500 From: Ed Maste <emaste@freebsd.org> To: Paul Floyd <pjfloyd@wanadoo.fr> Cc: "toolchain@freebsd.org" <toolchain@freebsd.org> Subject: Re: clang options for load segments Message-ID: <CAPyFy2BzBVX0Q1tB39CA-fXQj4b44MMVAhWOvi6fRaDPaEzs8g@mail.gmail.com> In-Reply-To: <89794bb8-5e97-36a7-0b6a-fa2eaf76a72a@wanadoo.fr> References: <fb3e3660-a6c0-c8ce-5055-624cde7ce95c@wanadoo.fr> <4D81BCDE-ECBC-49D8-BF17-38E334141FE0@FreeBSD.org> <89794bb8-5e97-36a7-0b6a-fa2eaf76a72a@wanadoo.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2 Mar 2021 at 14:37, Paul Floyd <pjfloyd@wanadoo.fr> wrote: > > I'll work on fixing it in Valgrind, but that is likely to be fair amount > of work. I guess that recent Clang+lld will produce the same PT_LOAD on Linux too, so it seems like this is definitely something Valgrind will need to handle. > No need to hold your breath. Concerning the FreeBSD port I've been > working on Valgrind on FreeBSD for about a year or so and now it's not > too far from working as well on FreeBSD as it does on Linux*. > > Either install the devel/valgrind-devel package (note: not > devel/valgrind) or even better build and install from my github repo > https://github.com/paulfloyd/freebsd_valgrind. I have a commit bit for > upstream Valgrind and am working on integrating FreeBSD support in the > 'official' Valgrind. This probably won't be in the next release, 3.17, > due soon, but I hope that it gets into the next one (3.17.1 or 3.18). > And I'm always on the lookout for any user feedback :-) . Thank you so much for this, I will be very happy to finally see FreeBSD support upstream. IMO we should look at removing devel/valgrind and replacing it with valgrind-devel, given the amount of not-upstream work that exists in both of them.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2BzBVX0Q1tB39CA-fXQj4b44MMVAhWOvi6fRaDPaEzs8g>