Bug 371831 - gcc does not generate DW_TAG_class_type
gcc does not generate DW_TAG_class_type
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: gcc (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Jakub Jelinek
Depends On: 426600
Blocks: 173278
  Show dependency treegraph
Reported: 2007-11-08 16:14 EST by Andrew Cagney
Modified: 2008-05-21 10:34 EDT (History)
3 users (show)

See Also:
Fixed In Version: RHBA-2008-0301
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-21 10:34:18 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Sourceware 5297 None None None Never

  None (edit)
Description Andrew Cagney 2007-11-08 16:14:38 EST
Instead it generates DW_ATE_struct_type; and heuristics get used to identify a
class rather than a type.  In a struct, default accessability is public, while
for a class it is private.
Comment 1 Jakub Jelinek 2007-12-21 14:00:31 EST
If RHEL5.2 gdb will handle it, Alex' patch can be backported.
Comment 2 RHEL Product and Program Management 2007-12-21 14:04:18 EST
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
Comment 8 errata-xmlrpc 2008-05-21 10:34:18 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. 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.