Joe Halpin wrote:
> Daniel Stenberg wrote:

> It looks like a problem with valgrind. When the command is run it sets
> the --logfile-fd=3 option, which results in the response
> /usr/libexec/ld-elf.so.1: Cannot open
> "/usr/local/lib/valgrind/vg_inject.so". It's there, and permissions are ok.
>
> Stay tuned, I'll get with the port maintainer and see if he knows what's
> going on.

I found where it's happening and let the maintainer know. Valgrind plays
  games with how memory is setup, so I'm going to let him figure it out.
However, he doesn't sound like he considers this a priority.

Another possibility is to modify runtests.pl to redirect stdout to the
logfile, something like

$CURL="exec 3>log/valgrind$testnum valgrind --leak-check=yes -q $CURL >&3";

This would work on both linux and freebsd. I've played around with it a
bit and I can get it to work if you're interested in going that way. I
could also add some code to use watchmalloc on Solaris as well.

Let me know if you're interested in that.

Joe
Received on 2004-04-18