Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Carlos Eduardo Seo <cseo@linux.vnet.ibm.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: 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 20:14:00 -0000	[thread overview]
Message-ID: <46D5D3AE.4010209@linux.vnet.ibm.com> (raw)
In-Reply-To: <20070829184824.GG3795@adacore.com>

[-- Attachment #1: Type: text/plain, Size: 692 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


>
> Cool!  Carlos, would you be able to look into that? I promise to
> review any patch promptly.
>
Joel

I believe this simple fix addresses the issue. It also fixes one thing
that was wrong with the previous patch: GDB was showing "{...}" when a
struct had no members, instead of <no data fields>.

What do you think?

- --
Carlos Eduardo Seo
Software Engineer
IBM Linux Technology Center
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG1dOuqvq7Aov/qQARAuiXAJ9l6SplkC3rw0yWirpfykMUIeozKQCdE+Nz
ozaauc2l8paWiDR/t3NUCtQ=
=egcI
-----END PGP SIGNATURE-----


[-- Attachment #2: ptype_unnamed.diff --]
[-- Type: text/plain, Size: 717 bytes --]

2007-08-16   Carlos Eduardo Seo <cseo@linux.vnet.ibm.com>

        gdb/c-typeprint.c (c_type_print_base): allows GDB to
	show members of unnamed struct/union that couldn't be
	displayed otherwise using ptype.

Index: src/gdb/c-typeprint.c
===================================================================
--- src.orig/gdb/c-typeprint.c	2007-08-29 12:36:09.000000000 -0700
+++ src/gdb/c-typeprint.c	2007-08-29 12:57:51.000000000 -0700
@@ -733,7 +733,7 @@
 	    fputs_filtered (" ", stream);
 	}
       wrap_here ("    ");
-      if (show < 0)
+      if ((show < 0) && (TYPE_TAG_NAME (type) != NULL))
 	{
 	  /* If we just printed a tag name, no need to print anything else.  */
 	  if (TYPE_TAG_NAME (type) == NULL)

[-- Attachment #3: ptype_unnamed.diff.sig --]
[-- Type: application/octet-stream, Size: 65 bytes --]

  parent reply	other threads:[~2007-08-29 20:14 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
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 [this message]
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=46D5D3AE.4010209@linux.vnet.ibm.com \
    --to=cseo@linux.vnet.ibm.com \
    --cc=brobecker@adacore.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