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

diff --git a/pym/portage/__init__.py b/pym/portage/__init__.py
index 0ffcc53365ae6bf3b612edd29a3ecf0170b2401e..ff40f2f5c7d2b886369c0cb54499dad36b2e1f77 100644 (file)
--- 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):