[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-wget] [bug-wget] Segfault when trying to use metalinks

From: Ángel González
Subject: Re: [Bug-wget] [bug-wget] Segfault when trying to use metalinks
Date: Sun, 08 Sep 2013 23:14:13 +0200
User-agent: Thunderbird

On 08/09/13 14:44, Darshit Shah wrote:

    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:

└─(~/testing)─(14 files, total 704Kb)─> valgrind --leak-check=full ./wget --metalink metalink
==29833== Memcheck, a memory error detector
==29833== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
==29833== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info
==29833== Command: ./wget --metalink metalink
==29833== Invalid write of size 4
==29833==    at 0x440FFA: fill_ranges_data (multi.c:148)
I bet an assert(i < opt.jobs); at multi.c:148 would fail.
I'm not sure how this code is supposed to work, but work from there.

It's funny how valgrind itself segfaulted, valgrind developers would probably be interested in that.

Don't worry about the sendmsg() warning from libc (it's shoud have been suppressed imho).

The leaks are something to fix, but not as critical as the segfault :)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]