
powerman at powerman
Jan 4, 2012, 2:43 PM
Post #2 of 4
(290 views)
Permalink
|
|
Re: New glibc feature caught sed in action while revdep-rebuild?
[In reply to]
|
|
Hi! On Wed, Jan 04, 2012 at 11:12:23PM +0100, "T髏h Attila" wrote: > On two systems I got the following messages while running revdep-rebuild. > What should I do next? ... > *** glibc detected *** sed: double free or corruption (!prev): 0x11770008 *** I've seen that before few times (with different apps, not sure about sed). If I remember correctly, it was fixed after full system recompile: # backup (just in case) and cleanup PKGDIR pkgdir=$(portageq pkgdir) mv $pkgdir /tmp/portage-packages install -d -o portage -g portage $pkgdir # recompile everything in most safest way emerge linux-headers glibc binutils gcc-config gcc && emerge -1 libtool && emerge -b glibc binutils gcc portage && emerge -bke system && emerge -ke world -- WBR, Alex.
|