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.

Created attachment 951024 [details]
Test output

Filed from caserun (https://tcms.engineering.redhat.com/run/188719/#caserun_7760463)

Test checking that gdb can pretty-print various PyObject* types

Version-Release number of selected component (if applicable):
----------
python-debug-2.7.5-18.bs4.ppc64le

Steps to Reproduce: 
1. run test /CoreOS/python/Sanity/gdb


Actual results: 
test_NULL_instance_dict (__main__.PrettyPrintTests)
Ensure that a PyInstanceObject with with a NULL in_dict is handled ... FAIL
test_NULL_ob_type (__main__.PrettyPrintTests)
Ensure that a PyObject* with NULL ob_type is handled gracefully ... FAIL
<snip>

Full output attached.

Expected results:
All test passed.

Thanks Slavek for investigation. This has been fixed by modifying our test case to use 'set print address off' setting.

Explanation:

# The tests assume that the first frame of printed
# backtrace will not contain program counter,
# that is however not guaranteed by gdb (rhbz#1125657)
# therefore we need to use 'set print address off' to
# make sure the counter is not there. For example:
# #0 in PyObject_Print ...
# is assumed, but sometimes this can be e.g.
# #0 0x00003fffb7dd1798 in PyObject_Print ...

Great, I'll just add the reference to the dist-git commit [1], where I used the same approach to fix Python's test suite. Brano, can we close this bug now?

[1] http://pkgs.devel.redhat.com/cgit/rpms/python/commit/?h=rhel-7.1&id=445b42ea123a0607442b501d6e71ab955c9fdd90

Sure. Closing.