Red Hat Bugzilla – Bug 609220
Various obstack-related memory corruptions
Last modified: 2016-09-19 22:07:03 EDT
+++ 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 email@example.com 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:
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.
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
# runtest --tool=gdb gdb.cp/pr10687.exp gdb.cp/pr9167.exp gdb.cp/static-print-quit.exp
=== gdb Summary ===
# of expected passes 11
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.