Bug 591993 - crash on VLA bound referencing optimized-out variable
crash on VLA bound referencing optimized-out variable
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gdb (Show other bugs)
x86_64 Linux
high Severity high
: rc
: ---
Assigned To: Jan Kratochvil
Petr Muller
Depends On: 591879
  Show dependency treegraph
Reported: 2010-05-13 12:13 EDT by Jan Kratochvil
Modified: 2016-09-19 22:06 EDT (History)
4 users (show)

See Also:
Fixed In Version: gdb-7.1-21.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 591879
Last Closed: 2010-07-02 15:08:09 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jan Kratochvil 2010-05-13 12:13:51 EDT
+++ This bug was initially created as a clone of Bug #591879 +++

abrt 1.1.0 detected a crash.

Was attempting to debug empathy:

(gdb) print *context->groups->data
Segmentation fault (core dumped)

--- Additional comment from jan.kratochvil@redhat.com on 2010-05-13 12:10:23 EDT ---

Great bugreport, thanks.
Checked-in now in archer-jankratochvil-vla as:

New testcase:
PASS: gdb.dwarf2/dw2-bound-loclist.exp: p b_string
PASS: gdb.dwarf2/dw2-bound-loclist.exp: ptype b_string
Comment 1 RHEL Product and Program Management 2010-05-13 12:37:04 EDT
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
Comment 4 releng-rhel@redhat.com 2010-07-02 15:08:09 EDT
Red Hat Enterprise Linux Beta 2 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.

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