[pacman-dev] [BUG] segfault when the download fails

[Dan McGee]

On Dec 6, 2007 5:46 PM, Xavier <shiningxc at gmail.com> wrote:
> I believe my mirror gave me a way to reproduce easily the issue Nagy
> described there :
> http://bugs.archlinux.org/task/8350#comment20223
>
> However, it doesn't look at all like the output in the original bug report,
> where the progress bar is at 64%. So I wasn't sure where to report this
> information, so I'm reporting it here for now before investigating further.
>
> Here is the --debug output:
>
> Targets: hunspell-1.2.1-2  openoffice-fr-2.3.1-1
>
> Total Download Size:    15.08 MB
>
> [00:27:01] debug: using cachedir: /var/cache/pacman/pkg/
> :: Retrieving packages from extra...
> error: Internal pacman error: Segmentation fault.
> Please submit a full bug report with --debug if appropriate.
> [00:27:01] debug: using 'hunspell-1.2.1-2-i686.pkg.tar.gz' for download
> progress
> [00:27:01] debug: connected to mir1.archlinuxfr.org successfully
> [00:27:02] debug: using 'openoffice-fr-2.3.1-1-i686.pkg.tar.gz' for download
> progress
> [00:27:02] error: failed retrieving file
> 'openoffice-fr-2.3.1-1-i686.pkg.tar.gz' from mir1.archlinuxfr.org : Not Found
> [00:27:02] debug: using 'hunspell-1.2.1-2-i686.pkg.tar.gz' for download
> progress
> [00:27:02] error: segmentation fault
>
> So pacman first downloads hunspell-1.2.1-2-i686.pkg.tar.gz and succeeds, then
> it tries to download openoffice-fr-2.3.1-1-i686.pkg.tar.gz and fails.
> So after that, it tries using the second server in the list. It starts with
> hunspell-1.2.1-2-i686.pkg.tar.gz again, and then bam, segfault.
>
> While I'm finishing this mail, the bug is already gone, since that package is
> now available on my first mirror. But when it wasn't available, the issue was
> 100% reproducible, I made it happen 10 times in a row.

I caught a segfault the other day during a big upgrade when one of the
xfce4 packages was missing on my first mirror. It segfaulted after
downloading everything else, it appeared.

This is an interesting bug and we might just get to the bottom of this
now that we at least have our conditions narrowed down.

-Dan