public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "drow at mvista dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/10499] [3.3, 3.4] Debug information for some C++ headers is missing classes (template specific?)
Date: Tue, 15 Jul 2003 20:50:00 -0000 [thread overview]
Message-ID: <20030715205021.13094.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030425143600.10499.drow@mvista.com>
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10499
------- Additional Comments From drow at mvista dot com 2003-07-15 20:50 -------
Subject: Re: [3.3, 3.4] Debug information for some C++ headers is missing classes (template specific?)
On Sat, Jul 05, 2003 at 02:55:08PM -0000, pinskia at physics dot uc dot edu wrote:
> Can you look at the output and tell me if this bug still exists?
What's the debugging output you put in the bug log from? There's no
basic_iostream in this testcase at all. From the readelf output, the
bug is still there.
next prev parent reply other threads:[~2003-07-15 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030425143600.10499.drow@mvista.com>
2003-07-05 14:55 ` pinskia at physics dot uc dot edu
2003-07-15 20:50 ` drow at mvista dot com [this message]
2003-07-24 19:00 ` pinskia at physics dot uc dot edu
2003-08-23 1:51 ` [Bug debug/10499] " dhazeghi at yahoo dot com
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=20030715205021.13094.qmail@sources.redhat.com \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).