On Fri, 21 Oct 2005 11:24:45 -0700, Judd Vinet wrote: > It's somewhere in pacman's cleanup code. It's probably > double-free'ing something at the end of a sync operation. The good > news is that all your upgrades will go through fine, since the > segfault doesn't occur until after all upgrades are complete. > > Again, if anyone can reproduce this, send me your pacman db BEFORE you > sucessfully upgrade! The problem with this segfault (for me, anyway) > is that once I see it, it's already too late and I can't get it to > reproduce. I haven't seen it on my own boxes yet.
I'd like to send you my package db again, but I'm not sure exactly what stage you want it at. On a newly installed system, at what step would you like the package db snapshot to be taken: 1. # pacman -S apr apr-util 2. # pacman -S apache Segfault (but apache was successfully installed) 3. # pacman -S apache Success (but only overwrites the already-working apache) The problem is that - like you write - the segfault occurs after the upgrade, so there isn't anything exciting in the package db neither before nor after the segfault. The only reason to fix this bug is that it probably causes cold sweat for most users that experience it (and doesn't know it's harmless) :-) _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
