2009/5/8 Xin LI :
> That's "Revision 352" and not 3.52 nor 3.5.2...
Ah, it's clear now.
> As far as I am aware Peter Wemm worked on a valgrind port which is
> available on p4. Haven't give it a twist yet as it seems that we need
> more work for amd64...
Is it checked into the ports tree?
Suppor
2009/5/8 Sergey Zaharchenko :
> Hardly an alternative, but devel/leaktracer might be of some help.
> That's what I use. This is C++ only.
I've tried it. Using is like a breathe. And does it's job.
Thank you.
Alexander Churanov
___
freebsd-ports@freebsd.
Hello Alexander!
Tue, May 05, 2009 at 04:28:20PM +0400 you wrote:
> Hi all!
>
> I am also interested in it. I have lots of questions about valgrind:
>
> 1) Is it working at all? I always receive SIGBUS on 7x.
> 2) Is our valgrind from http://valgrind.org/ or valgrind.kde.org?
> 3) valgrind.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexander Churanov wrote:
> Hi all!
>
> I am also interested in it. I have lots of questions about valgrind:
>
> 1) Is it working at all? I always receive SIGBUS on 7x.
> 2) Is our valgrind from http://valgrind.org/ or valgrind.kde.org?
> 3) valgrind
Hi all!
I am also interested in it. I have lots of questions about valgrind:
1) Is it working at all? I always receive SIGBUS on 7x.
2) Is our valgrind from http://valgrind.org/ or valgrind.kde.org?
3) valgrind.org lists 3.4.1 as latest release, but there is 3.52 in
ports, how is it possible?
I
Hi, all
I donot know whether it is suitable to post it here, but I am now looking
for some information about porting valgrind to FreeBSD.
Could somebody give me some information about the progress in porting
valgrind to FreeBSD? Or the mainpage for the porting project?
Regards
lifengkai
___
