Darshit Shah <[email protected]> writes: >> Try running the segfaulting metalink wget under valgrind. >> > > As Angel suggested, I ran the wget with the said metalink file through > valgrind. THe results are quite surprising: > All the leaks seem to originate from the metalink related code. There do > exist a few leaks in the Wget trunk code, but they did not prop up here.
thanks for your report. I know the metalink support is still very unstable in the parallel-wget branch, that is why it is not yet merged into master. The parallel branch is quite hacky at the moment, so the plan is to merge your new test-suite first and after proceed with a refactor of the parallel-wget branch. Unfortunately the parallel-wget code is quite hacky and it requires some refactoring, that can be done in a safer way with your new tests. Giuseppe
