Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Paul Hilfinger <Hilfinger@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: Question on typedefs of anonymous structs in G++
Date: Wed, 07 May 2008 11:39:00 -0000	[thread overview]
Message-ID: <20080507113851.GA32216@caradoc.them.org> (raw)
In-Reply-To: <20080507090045.51A1048CC44@nile.gnat.com>

On Wed, May 07, 2008 at 05:00:45AM -0400, Paul Hilfinger wrote:
> produces no trace of debugging information about Foo.  Serves one
> right for writing a C-style definition of Foo in a C++ program, to be
> sure, but G++ used to include Foo in the debugging data.  Does anyone
> here happen to know the story behind the change?  Thanks.

It is presumably just a bug (if the type is used somewhere); I suggest
verifying it on HEAD and putting it in gcc's bugzilla.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-05-07 11:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-07  9:01 Paul Hilfinger
2008-05-07 11:39 ` Daniel Jacobowitz [this message]
2008-05-08 19:15 ` Michael Snyder

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=20080507113851.GA32216@caradoc.them.org \
    --to=drow@false.org \
    --cc=Hilfinger@adacore.com \
    --cc=gdb@sourceware.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