public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/python+doco/NEWS] Add gdb.Type.name attribute.
Date: Tue, 07 Jan 2014 03:14:00 -0000	[thread overview]
Message-ID: <20140107031434.GG3802@adacore.com> (raw)
In-Reply-To: <87vbxwkcpa.fsf@fleche.redhat.com>

> >>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
> 
> Joel>         * python/py-type.c (typy_get_name): New function.
> Joel>         (type_object_getset): Add entry for attribute "name".
> Joel>         * NEWS: Add entry mentioning this new attribute.
> 
> Joel>         * py-pp-integral.c: New file.
> Joel>         * py-pp-integral.py: New file.
> Joel>         * py-pp-integral.exp: New file.
> 
> Joel> Tested on x86_64-linux. OK to commit?
> 
> Thanks Joel.  This is ok.

Thanks, Tom and Eli for the reviews. The patch is now in.

> Note that scalar types are often lost by gdb, so if you want to try
> "print (our_time_t) value", it will probably not work.  This is fallout
> from check_typedef.  There's a bug in bugzilla about this.

I see. I've noticed the same problem with Ada as well, but during
internal transformations (what we call type "fix"-ing), where we lose
information as we go - Eg, we lose the type's name, or the type of
the array index, etc.  I've tried to fix things when they become
needed as well.

-- 
Joel

  reply	other threads:[~2014-01-07  3:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-23  3:37 Joel Brobecker
2013-12-23  3:54 ` Eli Zaretskii
2014-01-06 21:44 ` Tom Tromey
2014-01-07  3:14   ` Joel Brobecker [this message]
2014-01-09 18:55 ` Tom Tromey
2014-01-10  4:02   ` 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=20140107031434.GG3802@adacore.com \
    --to=brobecker@adacore.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).