From: Tom Tromey <tromey@redhat.com>
To: Daniel Jacobowitz <dan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] Delay reading of struct members
Date: Fri, 10 Sep 2010 12:18:00 -0000 [thread overview]
Message-ID: <m3r5h2pscy.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100909203214.GY28036@caradoc.them.org> (Daniel Jacobowitz's message of "Thu, 9 Sep 2010 16:32:15 -0400")
>>>>> "Daniel" == Daniel Jacobowitz <dan@codesourcery.com> writes:
Daniel> Well, I thought the difference was that the source code said "struct X
Daniel> { }", and GDB displayed "class X { }". Which was GCC PR 7081, fixed
Daniel> many moons ago. But it looks like it's the other way round; RealView
Daniel> was incorrectly displaying "struct X { }". Sorry for the confusion!
No problem. It is always nice when the GNU toolchain doesn't have a bug :-)
Tom
prev parent reply other threads:[~2010-09-09 20:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 20:39 Daniel Jacobowitz
2010-09-09 13:14 ` Daniel Jacobowitz
2010-09-09 20:36 ` Tom Tromey
2010-09-09 23:32 ` Daniel Jacobowitz
2010-09-10 12:18 ` Tom Tromey [this message]
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=m3r5h2pscy.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dan@codesourcery.com \
--cc=gdb-patches@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