Summary: | app-emulation/vmware-workstation-5.5.0.18463 build failure (segmentation fault) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michael Lee Yohe <aksansai> |
Component: | New packages | Assignee: | Gentoo VMWare Bug Squashers [disabled] <vmware+disabled> |
Status: | VERIFIED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Michael Lee Yohe
2005-11-28 13:54:13 UTC
Boot with an InstallCD and run memtest86 overnight. If you're getting a segmentation fault out of tar, you've got problems other than VMware... ;] Some things to look for: - failing memory - overheating system - failing CPU memtest86 reports no problems. I haven't had a problem with _any_ of the previous 5.0 builds. Funny diagnosis, really. /usr/lib/portage/bin/ebuild.sh: line 360: 10340 Segmentation fault tar xzf "${DISTDIR}/${x}" ${tarvars} That is basically saying that line 360 from ebuild.sh, which is the line that runs this tar command, which segfaulted, is the source of the error. Basically, it is saying that tar crashed. This has nothing to do with the vmware ebuild, it just happened to occur when you were merging vmware. You can try again and see if you have the same issue, but I'm leaning towards something being wrong with your system in the way of hardware. Also, there's no chance that you ran "memtest86 overnight" when I posted only an hour before you. Unless you have a *very* tiny amount of RAM, not even a single pass would complete in that amount of time, let alone doing multiple passes to ensure it isn't an intermittent problem. |