summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorZac Medico <zmedico@gentoo.org>2008-11-22 18:47:19 +0000
committerZac Medico <zmedico@gentoo.org>2008-11-22 18:47:19 +0000
commit7084ae3b52fbf81b3b452cfa6f5de2a05ecedd69 (patch)
tree376b9b24a70d624dd63407885ffa13af4ef3e049
parent2d9c7e1d221d84ca80bb2c30416a019f55136601 (diff)
downloadportage-7084ae3b52fbf81b3b452cfa6f5de2a05ecedd69.tar.gz
portage-7084ae3b52fbf81b3b452cfa6f5de2a05ecedd69.tar.bz2
portage-7084ae3b52fbf81b3b452cfa6f5de2a05ecedd69.zip
Add some hints about bash binary corruption and hardware malfunction to the
message that's displayed when bash exits unexpectedly. svn path=/main/trunk/; revision=12041
-rw-r--r--pym/portage/__init__.py4
1 files changed, 3 insertions, 1 deletions
diff --git a/pym/portage/__init__.py b/pym/portage/__init__.py
index 36e055f91..e711c6b26 100644
--- a/pym/portage/__init__.py
+++ b/pym/portage/__init__.py
@@ -5131,7 +5131,9 @@ def _doebuild_exit_status_check(mydo, settings):
"is known to be triggered " + \
"by things such as failed variable " + \
"assignments (bug #190128) or bad substitution " + \
- "errors (bug #200313)."
+ "errors (bug #200313). This behavior may also be " + \
+ "triggered by a corrupt bash binary or a hardware " + \
+ "problem such as memory or cpu malfunction."
return msg
def _doebuild_exit_status_check_and_log(settings, mydo, retval):