public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/15464] Accessing anonymous unions from Python
Date: Tue, 14 Jan 2014 01:44:00 -0000	[thread overview]
Message-ID: <bug-15464-4717-AE9DjKhTsg@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15464-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=15464

--- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gdb and binutils".

The branch, master has been updated
       via  b5b08fb4ffa53ec088f8ad865bee0fd6edb2906f (commit)
      from  13aaf454542c1028a033ac836d7a0d47c63a7029 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b5b08fb4ffa53ec088f8ad865bee0fd6edb2906f

commit b5b08fb4ffa53ec088f8ad865bee0fd6edb2906f
Author: Siva Chandra <sivachandra@chromium.org>
Date:   Fri Dec 27 12:20:59 2013 -0800

    Use bitpos and type to lookup a gdb.Field object when its name is 'None'.

        PR python/15464
        PR python/16113
        * valops.c (value_struct_elt_bitpos): New function
        * py-type.c (convert_field): Set 'name' attribute of a gdb.Field
        object to 'None' if the field name is an empty string ("").
        * python/py-value.c (valpy_getitem): Use 'bitpos' and 'type'
        attribute to look for a field when 'name' is 'None'.
        (get_field_type): New function

        testsuite/
        * gdb.python/py-type.c: Enhance test case.
        * gdb.python/py-value-cc.cc: Likewise
        * gdb.python/py-type.exp: Add new tests.
        * gdb.python/py-value-cc.exp: Likewise

-----------------------------------------------------------------------

Summary of changes:
 gdb/ChangeLog                            |   11 ++++
 gdb/python/py-type.c                     |   15 ++++--
 gdb/python/py-value.c                    |   80 ++++++++++++++++++++++++-----
 gdb/testsuite/ChangeLog                  |    9 +++
 gdb/testsuite/gdb.python/py-type.c       |    9 +++
 gdb/testsuite/gdb.python/py-type.exp     |    9 +++
 gdb/testsuite/gdb.python/py-value-cc.cc  |   23 +++++++++
 gdb/testsuite/gdb.python/py-value-cc.exp |   20 +++++++
 gdb/valops.c                             |   45 +++++++++++++++++
 gdb/value.h                              |    5 ++
 10 files changed, 208 insertions(+), 18 deletions(-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2014-01-14  1:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-14  9:36 [Bug python/15464] New: " andre.poenitz at digia dot com
2013-05-14 13:26 ` [Bug python/15464] " tromey at redhat dot com
2013-12-27  6:38 ` tromey at redhat dot com
2013-12-30 17:03 ` poenitz at htwm dot de
2014-01-14  1:44 ` cvs-commit at gcc dot gnu.org [this message]
2014-01-15 13:12 ` cvs-commit at gcc dot gnu.org

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=bug-15464-4717-AE9DjKhTsg@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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).