summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKarel Klic <kklic@redhat.com>2010-07-09 14:09:42 +0200
committerKarel Klic <kklic@redhat.com>2010-07-09 14:09:42 +0200
commit8d74c0d2c3fa5df88d7cd85e543d4a90919489c6 (patch)
tree90b6718b6f1a3e602cd5fbebc5175e306dcccde1
parentccd23158a4dcbc633085412bd44d8a7f7f07558e (diff)
downloadabrt-8d74c0d2c3fa5df88d7cd85e543d4a90919489c6.tar.gz
abrt-8d74c0d2c3fa5df88d7cd85e543d4a90919489c6.tar.xz
abrt-8d74c0d2c3fa5df88d7cd85e543d4a90919489c6.zip
Suggest to not to save crashes from interactive shells
-rw-r--r--doc/INTERPRETED_LANGUAGES5
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/INTERPRETED_LANGUAGES b/doc/INTERPRETED_LANGUAGES
index 7de8f5c6..e79a1321 100644
--- a/doc/INTERPRETED_LANGUAGES
+++ b/doc/INTERPRETED_LANGUAGES
@@ -65,8 +65,9 @@ The file with the main entry point of the application. Might be a JAR
archive, a script file, a bytecode file, or the interpreter. It should
be a real file on the filesystem, so ABRT can check the origin of the
file (source package). If the file is not known, the most appropriate
-is to shortly describe the reason why it is not known in the field,
-e.g. "Exception raised from Python shell".
+is to shortly describe the reason why it is not known in the field.
+However, exceptions raised from interactive shell (a common reason
+for unknown file) are hardly useful and should not be reported.
ANALYZER
The name of an analyzer plugin which should be run during the