Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

+++ 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