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.

Bug 609220

Summary: Various obstack-related memory corruptions
Product: Red Hat Enterprise Linux 6 Reporter: Jan Kratochvil <jan.kratochvil>
Component: gdbAssignee: Jan Kratochvil <jan.kratochvil>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Muller <pmuller>
Severity: medium Docs Contact:
Priority: low    
Version: 6.0CC: ebachalo, ohudlick, pmuller
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:2ace2d86ef9ef95f4d44d02d09f42972e2eed420
Fixed In Version: gdb-7.1-27.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 606185 Environment:
Last Closed: 2010-11-10 20:27:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 606185    
Bug Blocks:    

Description Jan Kratochvil 2010-06-29 17:12:34 UTC
+++ This bug was initially created as a clone of Bug #606185 +++

reason: Process /usr/bin/gdb was killed by signal 11 (SIGSEGV)

--- Additional comment from tromey on 2010-06-21 23:53:30 CEST ---

#10 0x0000000000512dd5 in val_print_array_elements (
    type=<value optimized out>, valaddr=0x11e889e0 "", 
    address=140161173391296, stream=0x165c9b0, recurse=41342, 

That "recurse" value points at the problem.

Without more information I would guess that this is one of:

http://sourceware.org/bugzilla/show_bug.cgi?id=9067
http://sourceware.org/bugzilla/show_bug.cgi?id=9167
http://sourceware.org/bugzilla/show_bug.cgi?id=10687


There are various crashes and endless loops difficult to investigate more.  But upstream has some fixes of clear memory corruptions.  Such fixes should never harm.

Comment 1 RHEL Program Management 2010-06-29 17:23:10 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 4 Petr Muller 2010-08-03 14:36:27 UTC
# runtest --tool=gdb gdb.cp/pr10687.exp gdb.cp/pr9167.exp gdb.cp/static-print-quit.exp

(...)

                === gdb Summary ===

# of expected passes            11

Comment 5 releng-rhel@redhat.com 2010-11-10 20:27:18 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.