1260558 – Unexpected output from gdb on ppc64le

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.

Bug 1260558 - Unexpected output from gdb on ppc64le

Summary: Unexpected output from gdb on ppc64le

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	gdb
Sub Component:
Version:	7.2
Hardware:	ppc64le
OS:	Linux
Priority:	unspecified
Severity:	unspecified
Target Milestone:	rc
Target Release:	---
Assignee:	Jan Kratochvil
QA Contact:	Miroslav Franc
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2015-09-07 09:00 UTC by Robert Kuska
Modified:	2016-04-18 10:17 UTC (History)
CC List:	10 users (show)
Fixed In Version:	gdb-7.6.1-79.el7
Doc Type:	Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:	2015-11-19 13:03:55 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2015:2089	0	normal	SHIPPED_LIVE	gdb bug fix and enhancement update	2015-11-19 11:24:00 UTC

Description Robert Kuska 2015-09-07 09:00:18 UTC

Tests within test_gdb in python fails on ppc64le architecture because gdb produces unexpected output.

Examples of failures:
FAIL: test_NULL_ob_type (test.test_gdb.PrettyPrintTests)
Ensure that a PyObject* with NULL ob_type is handled gracefully
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/builddir/build/BUILD/Python-2.7.5/Lib/test/test_gdb.py", line 487, in test_NULL_ob_type
    'set op->ob_type=0')
  File "/builddir/build/BUILD/Python-2.7.5/Lib/test/test_gdb.py", line 454, in assertSane
    cmds_after_breakpoint=cmds_after_breakpoint)
  File "/builddir/build/BUILD/Python-2.7.5/Lib/test/test_gdb.py", line 234, in get_gdb_repr
    import_site=import_site)
  File "/builddir/build/BUILD/Python-2.7.5/Lib/test/test_gdb.py", line 219, in get_stack_trace
    self.assertEqual(unexpected_errlines, [])
AssertionError: Lists differ: ['[10927 refs]', 'No symbol "o... != []
First list contains 3 additional elements.
First extra element 0:
[10927 refs]
- ['[10927 refs]', 'No symbol "op" in current context.', 'No stack.']
+ []
======================================================================
FAIL: test_NULL_ptr (test.test_gdb.PrettyPrintTests)
Ensure that a NULL PyObject* is handled gracefully
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/builddir/build/BUILD/Python-2.7.5/Lib/test/test_gdb.py", line 479, in test_NULL_ptr
    'backtrace'])
  File "/builddir/build/BUILD/Python-2.7.5/Lib/test/test_gdb.py", line 234, in get_gdb_repr
    import_site=import_site)
  File "/builddir/build/BUILD/Python-2.7.5/Lib/test/test_gdb.py", line 219, in get_stack_trace
    self.assertEqual(unexpected_errlines, [])
AssertionError: Lists differ: ['[10927 refs]', 'No symbol "o... != []
First list contains 3 additional elements.
First extra element 0:
[10927 refs]
- ['[10927 refs]', 'No symbol "op" in current context.', 'No stack.']
+ []
======================================================================
FAIL: test_builtin_function (test.test_gdb.PrettyPrintTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/builddir/build/BUILD/Python-2.7.5/Lib/test/test_gdb.py", line 618, in test_builtin_function
    gdb_repr, gdb_output = self.get_gdb_repr('print len')
  File "/builddir/build/BUILD/Python-2.7.5/Lib/test/test_gdb.py", line 234, in get_gdb_repr
    import_site=import_site)
  File "/builddir/build/BUILD/Python-2.7.5/Lib/test/test_gdb.py", line 219, in get_stack_trace
    self.assertEqual(unexpected_errlines, [])
AssertionError: Lists differ: ['[10927 refs]', 'No stack.'] != []
First list contains 2 additional elements.
First extra element 0:
[10927 refs]
- ['[10927 refs]', 'No stack.']
+ []
======================================================================


Affected component:
gdb-7.6.1-78.el7

Comment 3 Jan Kratochvil 2015-09-07 22:03:29 UTC

[ppc64le] Use skip_entrypoint for skip_trampoline_code
https://sourceware.org/ml/gdb-patches/2015-09/msg00080.html
[ppc64le patch v2] Use skip_entrypoint for skip_trampoline_code
https://sourceware.org/ml/gdb-patches/2015-09/msg00081.html

RHEL-7.2 scratch build (running):
  https://brewweb.devel.redhat.com/taskinfo?taskID=9807307

Comment 8 errata-xmlrpc 2015-11-19 13:03:55 UTC

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://rhn.redhat.com/errata/RHBA-2015-2089.html

Note You need to log in before you can comment on or make changes to this bug.