Red Hat Bugzilla – Bug 1361116
`detected unhandled Python exception` error could be of more use
Last modified: 2018-04-10 13:43:10 EDT
+++ This bug was initially created as a clone of Bug #1361112 +++ Description of problem: The "detected unhandled Python exception" message could be more verbose. It denotes Python exceptions raised in interactive python or python executing script via "python -c "..."" Version-Release number of selected component (if applicable): abrt-2.0.8-40.el6.x86_64 abrt-python-2.0.8-40.el6.x86_64 How reproducible: Always Steps to Reproduce: 1.'python -c "1/0"' 2. check /var/log/messages 3. Actual results: abrt: detected unhandled Python exception Expected results: Origin of exception may be?
As with bug 1361112 we could change the message from the current form to: "detected unhandled Python exception in 'interactive mode (python -c)'" when "python -c ..." is executed, and: "detected unhandled Python exception in 'interactive mode'" when "python" or "python -i". In RHEL 7 you can get more information about the origin of the exception from systemd journal by typing: journalctl -a -S '1 day ago' -o verbose _COMM=python | grep 'MESSAGE\|_CMDLINE' This will print out log messages and commands that were launched and in which unhandled Python exception occurred. "MESSAGE=detected unhandled Python exception" "_CMDLINE=python -c 1/0"
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0949