summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorZac Medico <zmedico@gentoo.org>2008-11-22 18:48:39 +0000
committerZac Medico <zmedico@gentoo.org>2008-11-22 18:48:39 +0000
commit4f396d0bfdf81f9f790151da80dde0e75e0c20c2 (patch)
tree4710486074ba6a9483301a5cd6f725f3f55471dd
parentec611e9b6afadf46003c60a579745198b76ddf98 (diff)
downloadportage-4f396d0bfdf81f9f790151da80dde0e75e0c20c2.tar.gz
portage-4f396d0bfdf81f9f790151da80dde0e75e0c20c2.tar.bz2
portage-4f396d0bfdf81f9f790151da80dde0e75e0c20c2.zip
Add some hints about bash binary corruption and hardware malfunction to the
message that's displayed when bash exits unexpectedly. (trunk r12041) svn path=/main/branches/2.1.6/; revision=12042
-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 0ffcc5336..ff40f2f5c 100644
--- a/pym/portage/__init__.py
+++ b/pym/portage/__init__.py
@@ -5121,7 +5121,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):