public inbox for src-cvs@sourceware.org
help / color / mirror / Atom feed
From: sivachandra@sourceware.org
To: src-cvs@sourceware.org
Subject: gdb and binutils branch value_dynamic_type created. ff519ed3b11d2781e21b668d36674d672eb5ad54
Date: Mon, 07 Apr 2014 21:10:00 -0000	[thread overview]
Message-ID: <20140407211022.1354.qmail@sourceware.org> (raw)

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, value_dynamic_type has been created
        at  ff519ed3b11d2781e21b668d36674d672eb5ad54 (commit)

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

commit ff519ed3b11d2781e21b668d36674d672eb5ad54
Author: Siva Chandra <sivachandra@chromium.org>
Date:   Fri Mar 21 06:42:50 2014 -0700

    [python] Fix gdb.Value.dynamic_type for reference values.
    
    gdb.Value.dynamic_type is supposed to work for reference and pointer
    values.  However, the value object in the function 'valpy_get_dynamic_type'
    was being dereferenced using 'value_ind' irrespective of the value type
    being TYPE_CODE_PTR or TYPE_CODE_REF.  This patch fixes that to use
    'coerce_ref' for TYPE_CODE_REF values.
    
    ChangeLog:
    
    	* python/py-value.c (valpy_get_dynamic_type): Use coerce_ref to
    	dereference TYPE_CODE_REF values.
    
    	testsuite/
    	* gdb.python/py-value.c: Improve test case.
    	* gdb.python/py-value.exp: Add new test.

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


hooks/post-receive
-- 
gdb and binutils


                 reply	other threads:[~2014-04-07 21:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20140407211022.1354.qmail@sourceware.org \
    --to=sivachandra@sourceware.org \
    --cc=src-cvs@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).