FS#25918 - Pacman Segfaults During update

Attached to Project: Pacman
Opened by Jesse Frey (jessef) - Wednesday, 07 September 2011, 15:03 GMT
Last edited by Dan McGee (toofishes) - Thursday, 06 October 2011, 15:03 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To Dave Reisner (falconindy)
Architecture All
Severity Medium
Priority Normal
Reported Version 3.5.4
Due in Version 4.0.0
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary and Info:
Pacman segfaults during upgrade. Seems to be related to failed retries during downloads. pacman output included in attachment.

Steps to Reproduce:
not very reproducible. It has happened to me twice but I am uncertain of the conditions to reproduce it. After it crashes I just remove /var/lib/pacman/db.lck and it works fine. Both time it has happened after multiple failed download attempts.
   pacman.out (2.8 KiB)
This task depends upon

Closed by  Dan McGee (toofishes)
Thursday, 06 October 2011, 15:03 GMT
Reason for closing:  Deferred
Additional comments about closing:  Likely fixed in 4.0 with switch to libcurl, please reopen if this is not true.
Comment by Jesse Frey (jessef) - Wednesday, 07 September 2011, 15:07 GMT
I forgot to mention that this happened to me on a different machine which is an x86 machine so the architecture probably should be any.
Comment by Dave Reisner (falconindy) - Wednesday, 07 September 2011, 15:18 GMT
Is mirror.ancl.hawaii.edu the last mirror on your list? debug output or a backtrace on this would be lovely.
Comment by Jesse Frey (jessef) - Wednesday, 07 September 2011, 15:36 GMT
Attached is my pacman.dbg
I did not attach before because the crash was not visible in the output. mirror.ancl.hawaii.edu is not the last mirror.
can I get a backtrace after the fact? this problem does not happen regularly so would I have to run pacman from gdb all the time?
   pacman.dbg (9.6 KiB)
Comment by Dave Reisner (falconindy) - Wednesday, 07 September 2011, 15:39 GMT
Log isn't useful if it doesn't show the crash... The fact that its intermittent makes this fairly hard to troubleshoot. Given that libfetch goes away and our entire download codepath has changed for 4.0.0, I'm inclined to suggest that you wait for rc2 and try that out to see if you can reproduce it there.
Comment by Dave Reisner (falconindy) - Thursday, 22 September 2011, 17:39 GMT
Please retest this on pacman 4.0.0 rc2:

http://mailman.archlinux.org/pipermail/pacman-dev/2011-September/014415.html

Loading...