[pacman-dev] "memory clobber before allocated" -S bug

James Rosten seinfeld90 at gmail.com
Wed Jan 24 20:42:52 EST 2007


This is similar to what Travis reported, but instead of happening on packages
that exist it happens when pacman3 can't find the package in the db.
For example:

 [~]
 james->monkeybox : sudo pacman3 -S random_junk --debug=1
[20:23:18] debug: config: new section 'options'
[20:23:18] debug: config: logfile: /var/log/pacman.log
[20:23:18] debug: config: noupgrade: etc/passwd
[20:23:18] debug: config: noupgrade: etc/group
[20:23:18] debug: config: noupgrade: etc/shadow
[20:23:18] debug: config: noupgrade: etc/sudoers
[20:23:18] debug: config: noupgrade: etc/fstab
[20:23:18] debug: config: noupgrade: etc/raidtab
[20:23:18] debug: config: noupgrade: etc/mdadm.conf
[20:23:18] debug: config: noupgrade: etc/ld.so.conf
[20:23:18] debug: config: noupgrade: etc/inittab
[20:23:18] debug: config: noupgrade: etc/rc.conf
[20:23:18] debug: config: noupgrade: etc/rc.local
[20:23:18] debug: config: noupgrade: etc/modprobe.conf
[20:23:18] debug: config: noupgrade: etc/modules.conf
[20:23:18] debug: config: noupgrade: etc/lilo.conf
[20:23:18] debug: config: noupgrade: boot/grub/menu.lst
[20:23:18] debug: config: noupgrade: etc/mkinitrd.conf
[20:23:18] debug: config: holdpkg: pacman
[20:23:18] debug: config: holdpkg: glibc
[20:23:18] debug: config: new section 'current'
[20:23:18] debug: opening database 'current'
[20:23:18] debug: config: including /etc/pacman3.d/current
[20:23:18] debug: attempt to re-register the 'current' database, using existing
[20:23:18] debug: config: new section 'current'
[20:23:18] debug: attempt to re-register the 'current' database, using existing
[20:23:18] debug: config: new section 'extra'
[20:23:18] debug: opening database 'extra'
[20:23:18] debug: config: including /etc/pacman3.d/extra
[20:23:18] debug: attempt to re-register the 'extra' database, using existing
[20:23:18] debug: config: new section 'extra'
[20:23:18] debug: attempt to re-register the 'extra' database, using existing
[20:23:18] debug: config: new section 'community'
[20:23:18] debug: opening database 'community'
[20:23:18] debug: config: including /etc/pacman3.d/community
[20:23:18] debug: attempt to re-register the 'community' database, using existing
[20:23:18] debug: config: new section 'community'
[20:23:18] debug: attempt to re-register the 'community' database, using existing
[20:23:18] debug: opening database 'local'
[20:23:18] debug: loading package cache (infolevel=0) for repository 'current'
[20:23:18] debug: loading package cache (infolevel=0) for repository 'extra'
[20:23:18] debug: loading package cache (infolevel=0) for repository 'community'
[20:23:18] debug: package cache reloaded (infolevel=0x2) for repository 'current'
[20:23:18] debug: package cache reloaded (infolevel=0x2) for repository 'extra'
[20:23:18] debug: package cache reloaded (infolevel=0x2) for repository 'community'
[20:23:18] debug: returning error 31 from _alpm_sync_addtarget : could not find or read package

[20:23:18] debug: loading group cache for repository 'current'
[20:23:19] debug: package cache reloaded (infolevel=0x1) for repository 'current'
[20:23:19] debug: loading group cache for repository 'extra'
[20:23:19] debug: package cache reloaded (infolevel=0x1) for repository 'extra'
[20:23:19] debug: loading group cache for repository 'community'
[20:23:19] debug: package cache reloaded (infolevel=0x1) for repository 'community'
error: 'random_junk': not found in sync db
memory clobbered before allocated block
Aborted

Yet, (credit goes to Dan for finding this) doing the samething with
pacman3.static works perfectly.

~ Jamie / yankees26




More information about the pacman-dev mailing list