Pacman

Historical bug tracker for the Pacman package manager.

The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues

This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
Tasklist

FS#20617 - pacman 3.4.0 and libfetch: Segmentation fault when using FTP repository servers on x86_64

Attached to Project: Pacman
Opened by Ville Rantanen (iipe) - Thursday, 26 August 2010, 08:28 GMT
Last edited by Dan McGee (toofishes) - Friday, 08 October 2010, 12:47 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version 3.4.0
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Pacman gives a segmentation fault when syncing and refreshing (pacman -Sy) with an FTP repository server and if XferCommand is not set to use wget or curl instead of libfetch.

Additional info:
Output of "pacman -Sy --debug" as attachment
Contents of pacman.conf as attachment
Updating packages with "pacman -Su" works, the problem is with "pacman -Sy"
Probably an architecture-related bug, since I use 32bit Arch Linux on another computer and the bug is not reproducible there.

Steps to reproduce:
Run "pacman -Sy" without setting the XferCommand in pacman.conf and with an FTP server as one of the repository mirrors
Tested and reproduced with pacman >= 3.4.0, and with libfetch >= 2.30-3
Not reproducible after downgrading to pacman < 3.4.0
This task depends upon

Closed by  Dan McGee (toofishes)
Friday, 08 October 2010, 12:47 GMT
Reason for closing:  Fixed
Additional comments about closing:  Glibc fix.
Comment by Ville Rantanen (iipe) - Thursday, 26 August 2010, 08:30 GMT
Here is the correct pacman.conf. I uploaded a wrong version by mistake.
Comment by Xavier (shining) - Monday, 27 September 2010, 16:02 GMT
do you still have this issue ? is it 100% reproducible ?
could you try to get a backtrace ?
http://wiki.archlinux.org/index.php/Debug_-_Getting_Traces
Comment by Ville Rantanen (iipe) - Friday, 08 October 2010, 09:25 GMT
This seems like the same bug:
https://bugs.archlinux.org/task/21114

I still have the issue. It is 100% reproducible.

Downgrading glibc from 2.12.1-1 to 2.11.1-3 fixes the problem.

Using ppp version 2.4.5-1 also gives a segmentation fault that is also fixed by downgrading glibc. With ppp, I get the log message:
Oct 8 12:15:58 --- kernel: pppd[14652]: segfault at 7fff1f41bb9f ip 00007f465e3aeab5 sp 00007fff1f410260 error 6 in libnss_files-2.12.1.so[7f465e3a9000+b000]

I have compiled pacman and glibc with the additional "-g" flags and "!strip" option given in that wiki link, but I still don't get any additional debug information from pacman.
Comment by Xavier (shining) - Friday, 08 October 2010, 11:15 GMT
Try :
# gdb pacman
You should see this if you build properly with debug info :
Reading symbols from /usr/bin/pacman...done.

Then do :
(gdb) run -Sy
...
(gdb) bt full

And attach output of the backtrace if it looks good

Join #archlinux-pacman on freenode IRC if you need more help.
Comment by Allan McRae (Allan) - Friday, 08 October 2010, 11:21 GMT
> Downgrading glibc from 2.12.1-1 to 2.11.1-3 fixes the problem.

Try glibc-2.12.1-2
Comment by Ville Rantanen (iipe) - Friday, 08 October 2010, 11:59 GMT
glibc-2.12.1-2 fixed the problem. Thank you.

Loading...