FS#5561 - pacman segfault
Attached to Project:
Pacman
Opened by Bruno Obsomer (bobzomer) - Tuesday, 10 October 2006, 09:37 GMT
Opened by Bruno Obsomer (bobzomer) - Tuesday, 10 October 2006, 09:37 GMT
|
Details
When I run pacman -Su, I get a segmentation fault. It is
reproducible. Here is what is produced as output:
[root@bobzomer bruno]# pacman -Su :: perl-xml-simple: local (2.14-3) appears to be newer than repo (extra/2.14-2) :: Above packages will be skipped. To manually upgrade use 'pacman -S <pkg>' Targets: getmail-4.6.4-1 jack-audio-connection-kit-0.102.20-1 Total Package Size: 0.3 MB Proceed with upgrade? [Y/n] :: Retrieving packages from extra... warning: failed to get filesize for getmail-4.6.4-1.pkg.tar.gz failed downloading getmail-4.6.4-1.pkg.tar.gz from ftp.belnet.be: 550 getmail-4.6.4-1.pkg.tar.gz: No such file or directory warning: failed to get filesize for jack-audio-connection-kit-0.102.20-1.pkg.tar.gz failed downloading jack-audio-connection-kit-0.102.20-1.pkg.tar.gz from ftp.belnet.be: 550 jack-audio-connection-kit-0.102.20-1.pkg.tar.gz: No such file or directory connect: Connection refused error: cannot connect to archlinux.antesis.org connect: Connection refused error: cannot connect to archlinux.antesis.org *** glibc detected *** pacman: double free or corruption (fasttop): 0x085d78c0 *** ======= Backtrace: ========= /lib/libc.so.6[0x400ab750] /lib/libc.so.6(__libc_free+0x84)[0x400acda4] pacman[0x80604ee] pacman[0x805b731] pacman[0x805bdeb] pacman[0x80523c6] pacman[0x8055335] /lib/libc.so.6(__libc_start_main+0xd8)[0x4005d808] pacman[0x804a0a1] ======= Memory map: ======== 08048000-0806b000 r-xp 00000000 03:05 663971 /usr/bin/pacman 0806b000-0806c000 rw-p 00023000 03:05 663971 /usr/bin/pacman 0806c000-085f2000 rw-p 0806c000 00:00 0 [heap] 40000000-4001a000 r-xp 00000000 03:05 194323 /lib/ld-2.4.so 4001a000-4001b000 r--p 00019000 03:05 194323 /lib/ld-2.4.so 4001b000-4001c000 rw-p 0001a000 03:05 194323 /lib/ld-2.4.so 4001c000-4001d000 r-xp 4001c000 00:00 0 [vdso] 4001d000-40021000 rw-p 4001d000 00:00 0 40021000-40029000 r-xp 00000000 03:05 194376 /lib/libnss_files-2.4.so 40029000-4002b000 rw-p 00007000 03:05 194376 /lib/libnss_files-2.4.so 4002b000-4002f000 r-xp 00000000 03:05 194362 /lib/libnss_dns-2.4.so 4002f000-40031000 rw-p 00003000 03:05 194362 /lib/libnss_dns-2.4.so 40031000-40033000 rw-p 40031000 00:00 0 40036000-40047000 r-xp 00000000 03:05 341891 /usr/lib/libz.so.1.2.3 40047000-40048000 rw-p 00011000 03:05 341891 /usr/lib/libz.so.1.2.3 40048000-40162000 r-xp 00000000 03:05 194324 /lib/libc-2.4.so 40162000-40164000 r--p 00119000 03:05 194324 /lib/libc-2.4.so 40164000-40166000 rw-p 0011b000 03:05 194324 /lib/libc-2.4.so 40166000-4016a000 rw-p 40166000 00:00 0 40182000-40190000 r-xp 00000000 03:05 194361 /lib/libresolv-2.4.so 40190000-40192000 rw-p 0000d000 03:05 194361 /lib/libresolv-2.4.so 40192000-40194000 rw-p 40192000 00:00 0 40194000-4019e000 r-xp 00000000 03:05 342206 /usr/lib/libgcc_s.so.1 4019e000-4019f000 rw-p 00009000 03:05 342206 /usr/lib/libgcc_s.so.1 40200000-40221000 rw-p 40200000 00:00 0 40221000-40300000 ---p 40221000 00:00 0 bfc97000-bfcad000 rw-p bfc97000 00:00 0 [stack] Aborted I launch pacman with gdb to have a backtrace, but since I didn't recompile it with debugging symbol, I have no idea of the true name of fonctions in pacman source. The only thing I see is that the backtrace is different from previous pacman segfault bug report (16 frames instead of 10). (gdb) bt #0 0x4001c410 in __kernel_vsyscall () #1 0x40070731 in raise () from /lib/libc.so.6 #2 0x40071e29 in abort () from /lib/libc.so.6 #3 0x400a5cfb in __libc_message () from /lib/libc.so.6 #4 0x400ab750 in malloc_printerr () from /lib/libc.so.6 #5 0x400acda4 in free () from /lib/libc.so.6 #6 0x080604ee in ?? () #7 0x085d78c0 in ?? () #8 0xbf9b9028 in ?? () #9 0xbf9be148 in ?? () #10 0x0805b731 in ?? () #11 0x085d78c0 in ?? () #12 0x08068114 in _IO_stdin_used () #13 0x08072560 in ?? () #14 0xbf9c02e8 in ?? () #15 0x085d4720 in ?? () #16 0x00000000 in ?? () |
This task depends upon
Closed by Jan de Groot (JGC)
Tuesday, 10 October 2006, 13:06 GMT
Reason for closing: Duplicate
Additional comments about closing: This bug has been reported before. A duplicate bug with patch attached is available in this bugtracker.
Tuesday, 10 October 2006, 13:06 GMT
Reason for closing: Duplicate
Additional comments about closing: This bug has been reported before. A duplicate bug with patch attached is available in this bugtracker.