I did this
In one of my dev branches I run ./torture -t44 [num] to reproduce a specific problem. It has a memory leak, which valgrind detects.
It seems to trigger a perl error:
$ ./runtests.pl -t44 451
...
test 0451...[Variable from file that is JSON and URL encoded (with null byte)]
159 functions to make fail
Undefined subroutine &runner::valgrindparse called at runner.pm line 481.
I expected the following
See the valgrind output at the end of test.
curl/libcurl version
current git master
operating system
Linux
I did this
In one of my dev branches I run
./torture -t44 [num]to reproduce a specific problem. It has a memory leak, which valgrind detects.It seems to trigger a perl error:
I expected the following
See the valgrind output at the end of test.
curl/libcurl version
current git master
operating system
Linux