Red Hat Bugzilla – Bug 589714
correct cases where report library crashes when no user I/O is available
Last modified: 2010-11-10 16:29:10 EST
+++ This bug was initially created as a clone of Bug #589712 +++
These crashes need to be turned into error messages.
As part of this, implement a no-query option to the report command,
so that it's easy to test these cases.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
fixed in fedorahosted src repo.
please can you advice some way how to reproduce?
I found out TextIO is used as a fallback io, so I tried nohup but it still gives traceback.
[root@timothy plugins-basic]# nohup report /tmp/dummy-report.txt
nohup: ignoring input and appending output to `nohup.out'
[root@timothy plugins-basic]# cat ./nohup.out
Where do you want to send this report:
Choice (0-4): Traceback (most recent call last):
File "/usr/bin/report", line 160, in <module>
app = report.report(signature, io, **optsDict)
File "/usr/lib64/python2.6/site-packages/report/__init__.py", line 489, in report
choice = buildChoices(signature, io, config, rptopts)
File "/usr/lib64/python2.6/site-packages/report/__init__.py", line 463, in buildChoices
choice = io.queryChoice(_("Where do you want to send this report:"), choices)
File "/usr/lib64/python2.6/site-packages/report/io/TextIO.py", line 85, in queryChoice
choice = raw_input("Choice (0-%s): " % (count-1,))
IOError: [Errno 9] Bad file descriptor
This bz can only be tested by calling the library directly. The following python script would crash before this bz was fixed. It will/should not crash now.
The crash in comment #7 is a separate issue, and should be a separate bz.
Ok, traceback from Comment #7 is reported as new Bug #591920.
Sorry, bad bug number. Correct is Bug #640218.
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.