From: Joel Brobecker <brobecker@adacore.com>
To: Carlos Eduardo Seo <cseo@linux.vnet.ibm.com>,
Luis Machado <luisgpm@linux.vnet.ibm.com>,
gdb-patches@sourceware.org
Subject: Re: [patch] ptype: show members of an unnamed struct inside an union
Date: Wed, 29 Aug 2007 18:32:00 -0000 [thread overview]
Message-ID: <20070829183215.GF3795@adacore.com> (raw)
In-Reply-To: <20070829163021.GA32337@caradoc.them.org>
[-- Attachment #1: Type: text/plain, Size: 868 bytes --]
> In C, it would be "my_page_var.mapping". The union is transparent.
Oh, I see. (love to learn new things :).
Back to the issue at hand, it therefore seems pretty desirable to
enhance the debugger in that case. Unfortunately, I don't think
the proposed patch is correct, because it bases the logic on the
size of the union/struct instead of whether the field is anonymous
or not. Do you agree?
Just for easier reference, the patch was:
2007-08-16 Carlos Eduardo Seo <cseo@linux.vnet.ibm.com>
gdb/c-typeprint.c (c_type_print_base): check value of
TYPE_NFIELDS (type) when displaying members of an
unnamed struct inside an union.
This patch breaks the tests that I just posted for RFA:
http://www.sourceware.org/ml/gdb-patches/2007-08/msg00498.html
But otherwise is reported to not cause any other regression on
the testsuite.
--
Joel
[-- Attachment #2: ptype_issue.diff --]
[-- Type: text/plain, Size: 715 bytes --]
2007-08-16 Carlos Eduardo Seo <cseo@linux.vnet.ibm.com>
gdb/c-typeprint.c (c_type_print_base): check value of
TYPE_NFIELDS (type) when displaying members of an
unnamed struct inside an union.
Index: src-git/gdb/c-typeprint.c
===================================================================
--- src-git.orig/gdb/c-typeprint.c 2007-08-16 15:28:04.000000000 -0700
+++ src-git/gdb/c-typeprint.c 2007-08-16 15:29:07.000000000 -0700
@@ -735,7 +735,7 @@
fputs_filtered (" ", stream);
}
wrap_here (" ");
- if (show < 0)
+ if ((show < 0) && (TYPE_NFIELDS (type) == 0))
{
/* If we just printed a tag name, no need to print anything else. */
if (TYPE_TAG_NAME (type) == NULL)
next prev parent reply other threads:[~2007-08-29 18:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-16 22:39 Carlos Eduardo Seo
2007-08-24 15:48 ` Joel Brobecker
2007-08-24 16:02 ` Carlos Eduardo Seo
2007-08-24 17:39 ` Joel Brobecker
2007-08-28 17:14 ` Joel Brobecker
2007-08-28 19:03 ` Luis Machado
2007-08-28 20:04 ` Joel Brobecker
2007-08-28 20:12 ` Carlos Eduardo Seo
2007-08-28 20:34 ` Joel Brobecker
2007-08-29 2:56 ` Daniel Jacobowitz
2007-08-29 4:36 ` Joel Brobecker
2007-08-29 16:30 ` Daniel Jacobowitz
2007-08-29 18:32 ` Joel Brobecker [this message]
2007-08-29 18:36 ` Daniel Jacobowitz
2007-08-29 18:48 ` Joel Brobecker
2007-08-29 18:50 ` Carlos Eduardo Seo
2007-08-29 20:14 ` Carlos Eduardo Seo
2007-08-29 20:23 ` Daniel Jacobowitz
2007-08-29 20:26 ` Carlos Eduardo Seo
2007-08-29 20:41 ` Joel Brobecker
2007-08-29 20:44 ` Daniel Jacobowitz
2007-08-29 21:01 ` Joel Brobecker
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=20070829183215.GF3795@adacore.com \
--to=brobecker@adacore.com \
--cc=cseo@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=luisgpm@linux.vnet.ibm.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