From: Jim Blandy <jimb@zwingli.cygnus.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: gdb null ptr
Date: Tue, 07 Nov 2000 22:28:17 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205663@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205647@msgid-missing>
I don't think limiting the caching to C++ programs solves the problem.
If I understand the situation, the SGI compiler attaches a DW_AT_name
attribute to array types. We don't know whether this behavior occurs
only in C compilation units, or in C++ compilation units as well.
If the SGI compiler emits bogus names for array types in C++ code too,
then the same bug will reappear when debugging C++ code, even with
this patch applied.
I think the change to tag_type_to_type needs to be reverted
altogether. I understand that it provides substantial savings in
storage, but it's simply not correct.
next prev parent reply other threads:[~2000-11-07 22:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-03 2:19 [Linux-ia64] Re: gdb null ptr Jim Wilson
2000-11-03 13:32 ` Pete Wyckoff
2000-11-03 21:32 ` Kevin Buettner
2000-11-03 21:42 ` Jim Wilson
2000-11-03 23:02 ` Kevin Buettner
2000-11-04 3:20 ` Daniel Berlin
2000-11-07 22:28 ` Jim Blandy [this message]
2000-11-07 23:38 ` Daniel Berlin
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=marc-linux-ia64-105590678205663@msgid-missing \
--to=jimb@zwingli.cygnus.com \
--cc=linux-ia64@vger.kernel.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