Date: Mon, 18 Feb 2008 12:50:36 +0100 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: "Heiko Wundram \(Beenic\)" <wundram@beenic.net> Cc: freebsd-hackers@freebsd.org, "Christian S.J. Peron" <csjp@freebsd.org> Subject: Re: valgrind or workalike on FreeBSD/amd64 7.0/8.0? Message-ID: <86d4qu7ab7.fsf@ds4.des.no> In-Reply-To: <200802181010.44055.wundram@beenic.net> (Heiko Wundram's message of "Mon\, 18 Feb 2008 10\:10\:43 %2B0100") References: <47B1F8B7.7030803@delphij.net> <20080216235001.GA80694@sub.vaned.net> <20080218085323.GA1439@roadrunner.spoerlein.net> <200802181010.44055.wundram@beenic.net>
next in thread | previous in thread | raw e-mail | index | archive | help
"Heiko Wundram (Beenic)" <wundram@beenic.net> writes: > Ulrich Spoerlein <uspoerlein@gmail.com> writes: > > When will mere mortals like us get a chance to play with it? I found > > valgrind _very_ useful back in the 5.x and 6.x days. > I just wanted to say that I'd also be very interested in testing it > out (if you need testers for it), because currently I always (have to > try to) compile applications I want to memcheck (which is my main > reason for using valgrind) on Linux, which is a slight PITA. > > I'd be running it on i386, anyway. The ports version is a little outdated, but it works fine on i386. What peter@ and phk@ are doing in p4 is to port a newer version to FreeBSD and add amd64 support. Hopefully, the upstream vendor will adopt those patches so it doesn't have to be done over for every major valgrind release. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86d4qu7ab7.fsf>