From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb@sources.redhat.com
Subject: Re: GCC 3.4 vs GDB 6.1
Date: Thu, 08 Jan 2004 20:33:00 -0000 [thread overview]
Message-ID: <20040108203351.GA13956@nevyn.them.org> (raw)
In-Reply-To: <3FFDBE02.2030609@gnu.org>
On Thu, Jan 08, 2004 at 03:30:58PM -0500, Andrew Cagney wrote:
> (kind of a bit late but ...)
> Are there any "bugs" GDB would like to see fixed in GCC 3.4?
>
> I ask this 'cos GDB starting to really use GCC's DWARF 2 info means (per
> PPC 64) GDB is also identifying occasional problems in GCC's DWARF 2 code.
>
> I'm wondering if there are problems that people know about.
For the biggest one I know of, see the thread I started on gcc@ on ...
Monday? or last week? ... about when to emit debug info for C++
classes. The discussion trailed off without agreement. After that the
only huge one I knew about was DW_TAG_namespace, and we've got that
covered now.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-01-08 20:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 20:30 Andrew Cagney
2004-01-08 20:33 ` Daniel Jacobowitz [this message]
2004-01-09 8:57 ` Eli Zaretskii
2004-01-09 14:36 ` Daniel Jacobowitz
2004-01-10 11:54 ` Eli Zaretskii
2004-01-10 16:34 ` Daniel Jacobowitz
2004-01-08 21:24 Michael Elizabeth Chastain
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=20040108203351.GA13956@nevyn.them.org \
--to=drow@mvista.com \
--cc=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
/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