public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: kettenis@gnu.org
To: gcc-gnats@gcc.gnu.org
Subject: debug/2971: Type of variable is wrong in dwarf2 debugging info
Date: Sun, 27 May 2001 03:26:00 -0000	[thread overview]
Message-ID: <20010527102321.22310.qmail@sourceware.cygnus.com> (raw)

>Number:         2971
>Category:       debug
>Synopsis:       Type of variable is wrong in dwarf2 debugging info
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun May 27 03:26:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     kettenis@gnu.org
>Release:        GCC 3.0 20010525
>Organization:
>Environment:
alpha-unknown-freebsd5.0 and i586-pc-linux-gnu
>Description:
Compiling the attached test with -gdwarf-2 -dA, we find DW_AT_type of variable lave points
at the DW_TAG_const_type die constructed for the argument cc, instead of pointing directly
to the DW_TAG_base_type that represents type unsigned char.

This is a regression from GCC 2.95.2.

This is a similar problem as the one described in PR 2813 (and I shamelessly copied parts
of that report).  Apparently the fix for that problem wasn't complete.
The problem that when modified_type_die is called, a tree node for "const unsigned char"
isn't available, so qualified_type will be NULL.  As a result the newly created DIE for
"const unsigned char" is equated to the tree node for its base type.
>How-To-Repeat:

>Fix:
I'll send a patch later :-).
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="t.c"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="t.c"

aW50CnF1eDEgKGNvbnN0IHVuc2lnbmVkIGNoYXIgY2MpCnsKICB1bnNpZ25lZCBjaGFyIGxhdmUg
PSAnQic7Cn0K


             reply	other threads:[~2001-05-27  3:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-27  3:26 kettenis [this message]
2001-05-27  3:56 Mark Kettenis
2001-06-08  9:52 mmitchel
2001-06-08 15:35 mmitchel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010527102321.22310.qmail@sourceware.cygnus.com \
    --to=kettenis@gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).