On Sun, 11 Apr 2004, Joe Halpin wrote:

> A port of valgrind is now available for FreeBSD

That sounds great!

> and I've been trying to get the daily build to work with it. However, it
> keeps failing with "can't run ../curl".

Did you build with configure --disable-shared? If not, try that first. I
mostly do that myself so I tend to forget that when I add things that might
not work if libcurl is built shared. I think the valgrind usage is like that.

> Is there some kind of build dependency on valgrind if it's installed? If so
> I'll get with the maintainer of the port to see if the problem can be worked
> out.

The test script checks for valgrind (in the $PATH) and runs it to see that it
works somewhat before it is used. There's no other dependency. Note that
there's nothing in the test script (yet) that actually checks or uses the
output valgrind produces (it is just written to a separate file in the log/
directory). The reasons for this is:

1. OpenSSL produces heaps of valgrind errors and I've found no good way to
   filter out these errors from errors we would actually care about.

2. The built-in memory leak system is actually quite good and finds most leaks
   already.

I would of course like to see a valgrind output parser that alerts if valgrind
detects an error, but I haven't had time to write one up yet. I find the
valgrind output somewhat unfriendly to machineparse for this purpose.

-- 
     Daniel Stenberg -- http://curl.haxx.se -- http://daniel.haxx.se
      Dedicated custom curl help for hire: http://haxx.se/curl.html