Hi,

On 04:52 Fri 12 May 2006, Duncan wrote:
> Anders =?iso-8859-1?Q?Th=F8gersen?= <anderslt@...> posted
> 20060511230451.GC8675@..., excerpted below, on  Fri, 12 May
> 2006 01:04:51 +0200:
> 
> > I have been consistently getting a segfault when doing emerge sync.
> > This has happened 3 times all while at 51%:
> > 
> > 	[...]
> > 
> > 	Total bytes read: 3377649
> > 
> > 	wrote 381 bytes  read 3377649 bytes  14783.50 bytes/sec
> > 	total size is 133702955  speedup is 39.58
> > 
> > 	>>> Updating Portage cache:   51%Segmentation fault
> > 
> That's almost certainly a portage cache corruption issue, not a hardware
> problem, since it always happens at the same place when updating the cache.
> 
> Try emerge --metadata.  (I think that command works with old/stable
> portage, I'm running the ~amd64 portage-2.1-preX versions here, and have
> been since they went ~amd64.)  That should just update the cache without
> doing the sync part first.
> 
> If it's really the cache, that too will probably fail.  If it doesn't
> fail, try another  emerge --sync, as it should then be fixed.  If it did
> fail as it likely will, you'll need to delete the cache and then run
> emerge --metadata again, to rebuild it.

Sorry for the late reply,... 

I backed up /var/cache/edb as you suggested and began emerge --metadata,
... First segfault occurred at 31%.  Feeling bold i restarted the
command and this time it went all the way to the magic 51% where it
segfaulted as before.  From here every emerge --metadata results in a
segfault at 51% :-/

If I understand you correctly the problem of this segfault is due to a
specific file in the poretage tree.  To correct this problem must I then
locate this file?

I am a little puzzled...

Regards
/Anders


-- 
gentoo-amd64@g.o mailing list