Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: <tromey@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [RFC] display names of explicit typedefs for 'info types'
Date: Fri, 25 Jun 2010 07:36:00 -0000	[thread overview]
Message-ID: <001501cb1438$f89e2930$e9da7b90$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <m3y6e48k0j.fsf@fleche.redhat.com>

> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Tom Tromey
> Envoyé : Thursday, June 24, 2010 6:37 PM
> À : Pierre Muller
> Cc : gdb-patches@sourceware.org
> Objet : Re: [RFC] display names of explicit typedefs for 'info types'
> 
> >>>>> "Pierre" == Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>
> writes:
> 
> Pierre>   I was always puzzled by the fact that info types
> Pierre> did sometime not list types that I knew existed.
> Pierre>   The problem is that for types defined in C using `typedef '
> Pierre> only the definition part was displayed, but not the name of
> Pierre> the type itself.
> 
> Thanks for finding this.
> 
> Pierre> (gdb) ptype my
> Pierre> type = int
> Pierre> Here again, the original typedef name is completely lost ...
> 
> I think this is expected.  You can see the typedef if you use 'whatis'
> instead:
> 
> (gdb) whatis my
> type = myint
> 
> Pierre> 2010-06-22  Pierre Muller  <muller@ics.u-strasbg.fr>
> Pierre>         * c-typeprint.c (c_print_typedef): Append new type name
> for
> Pierre> typedefs.
> 
> This is ok.  Thanks.


  Thanks for the approval,
patch committed in:
http://sourceware.org/ml/gdb-cvs/2010-06/msg00167.html

Pierre


  reply	other threads:[~2010-06-25  7:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <37197.5782713436$1277308354@news.gmane.org>
2010-06-24 16:56 ` Tom Tromey
2010-06-25  7:36   ` Pierre Muller [this message]
2010-06-23 15:52 Pierre Muller
2010-06-23 16:58 ` 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='001501cb1438$f89e2930$e9da7b90$@muller@ics-cnrs.unistra.fr' \
    --to=pierre.muller@ics-cnrs.unistra.fr \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@redhat.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