From: Wu Zhou <woodzltc@cn.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
brobecker@adacore.com, gdb@sources.redhat.com,
gdb-testers@sources.redhat.com
Subject: Re: First release candidate for GDB 6.4 available
Date: Fri, 25 Nov 2005 04:21:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.63.0511251116540.22345@linux.site> (raw)
In-Reply-To: <20051125030852.GC20073@nevyn.them.org>
On Thu, 24 Nov 2005, Daniel Jacobowitz wrote:
> On Fri, Nov 25, 2005 at 10:53:50AM +0800, Wu Zhou wrote:
> > > ...
> > > > FAIL: gdb.cp/anon-union.exp: print w 1
> > > > FAIL: gdb.cp/anon-union.exp: print z 1
> > > > FAIL: gdb.cp/anon-union.exp: print w 2
> > > > FAIL: gdb.cp/anon-union.exp: print z 2
> > > > FAIL: gdb.cp/anon-union.exp: print w 3
> > > > FAIL: gdb.cp/anon-union.exp: print z 3
> >
> > I guess that GDB don't know how to handle anonymous union yet. I ever saw
> > these failures in a few platform. And also see them ok on others. The
> > difference I find is that some version of gcc handle the anonymous union
> > members as normal variables, others don't.
>
> I believe this was a bug in GCC 4.x, very recently fixed in CVS.
Sorry. What is a bug, handle the anonymous union as normal variable, or
don't?
Regards
- Wu Zhou
next prev parent reply other threads:[~2005-11-25 3:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 8:39 Joel Brobecker
2005-11-22 14:09 ` Daniel Jacobowitz
2005-11-25 5:28 ` Randolph Chung
2005-11-22 23:16 ` Ulrich Weigand
2005-11-22 23:20 ` info types question Stefan Burström
2005-11-22 23:45 ` Daniel Jacobowitz
2005-11-22 23:50 ` Stefan Burström
2005-11-25 3:09 ` Daniel Jacobowitz
2005-11-22 23:20 ` First release candidate for GDB 6.4 available Mark Kettenis
2005-11-23 5:17 ` Wu Zhou
2005-11-25 2:47 ` Mark Kettenis
2005-11-25 2:51 ` Wu Zhou
2005-11-25 3:15 ` Daniel Jacobowitz
2005-11-25 4:21 ` Wu Zhou [this message]
2005-11-25 15:57 ` Kunal Parmar
2005-11-28 22:44 ` Mark Kettenis
2005-11-23 19:34 Newman, Sarah R
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=Pine.LNX.4.63.0511251116540.22345@linux.site \
--to=woodzltc@cn.ibm.com \
--cc=brobecker@adacore.com \
--cc=drow@false.org \
--cc=gdb-testers@sources.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=mark.kettenis@xs4all.nl \
/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).