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.

Description of problem:
Just was debugging another crash.

Version-Release number of selected component:
gdb-7.6.1-80.el7

Additional info:
reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        gdb -c coredump
crash_function: value_type
executable:     /usr/bin/gdb
global_pid:     11996
kernel:         3.10.0-327.el7.x86_64
runlevel:       N 3
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 value_type at ../../gdb/value.c:765
 #1 py_print_single_arg at ../../gdb/python/py-framefilter.c:445
 #2 enumerate_args at ../../gdb/python/py-framefilter.c:628
 #3 py_print_args at ../../gdb/python/py-framefilter.c:967
 #4 py_print_frame at ../../gdb/python/py-framefilter.c:1229
 #5 apply_frame_filter at ../../gdb/python/py-framefilter.c:1506
 #6 backtrace_command_1 at ../../gdb/stack.c:1774
 #7 backtrace_command at ../../gdb/stack.c:1888
 #8 execute_command at ../../gdb/top.c:487
 #9 command_handler at ../../gdb/event-top.c:436

Created attachment 1093144 [details]
File: backtrace

Created attachment 1093145 [details]
File: cgroup

Created attachment 1093146 [details]
File: core_backtrace

Created attachment 1093147 [details]
File: dso_list

Created attachment 1093148 [details]
File: environ

Created attachment 1093149 [details]
File: exploitable

Created attachment 1093150 [details]
File: limits

Created attachment 1093151 [details]
File: machineid

Created attachment 1093152 [details]
File: maps

Created attachment 1093153 [details]
File: open_fds

Created attachment 1093154 [details]
File: proc_pid_status

Created attachment 1093155 [details]
File: var_log_messages

Created attachment 1093156 [details]
File: sosreport.tar.xz

Relevant binaries, debuginfo and core dump in the tarball:
http://people.freedesktop.org/~lkundrak/gdbcrash.tar.xz

[patch+7.8?] Fix crash on Python frame filters with unreadable arg
https://sourceware.org/ml/gdb-patches/2014-08/msg00364.html
Message-ID: <20140819215646.GA8129.net>

Due to a bug in the ABRT reporting tool, this bug report may have contained information that you did not intend to include.  As a precaution, we have made the bug report private.  You may wish to review the bug report in an effort to identify information that you inadvertently included in the bug report and take appropriate remedial action.

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-2016-2328.html