WINDOWS TIPS AND TRICK

1. Access the Bugzilla database, a debugging research database specifically for sandbox errors.
2. Find your sandbox error message within the error messages listed by using the “find” search tool and plugging in the exact language in your error message.
3. Examine the information provided about your specific sandbox error message to see if a fix is provided. If so, follow the directions for instituting the fix. If your specific error is not listed, use the fix provided for the error messages closest to yours.
4. Find the corrupted ebuild — if the above steps do not reveal the problem — using “Addpredict.” Access the sandbox shell and apply the Addpredict function to any suspect ebuild. The ebuild will be allowed to simulate a write to the live file system, which reveals a malfunctioning ebuild.