From: Siva Chandra <sivachandra@google.com>
To: gdb-patches <gdb-patches@sourceware.org>
Cc: Doug Evans <dje@google.com>
Subject: Re: [Python] Add methods reference_value and const_value to gdb.Value
Date: Mon, 04 May 2015 23:40:00 -0000 [thread overview]
Message-ID: <CAGyQ6gxxeAt14dpyyhxYid3FOWOwrumrKvd7FEmpxYoBrE51ug@mail.gmail.com> (raw)
In-Reply-To: <CAGyQ6gw3=nbXap4Uk2CP7h15UqNe7hoXuJj5+8D15BiC4d9u1w@mail.gmail.com>
Ping.
On Mon, Apr 27, 2015 at 6:30 AM, Siva Chandra <sivachandra@google.com> wrote:
> This will help address libstdc++/65840:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65840
>
> gdb/ChangeLog:
>
> 2015-04-27 Siva Chandra Reddy <sivachandra@google.com>
>
> * NEWS (Python Scripting): Mention the new gdb.Value methods.
> * python/py-value.c (valpy_reference_value): New function.
> (valpy_const_value): Likewise.
> (value_object_methods): Add new methods.
> * value.c (make_cv_value): New function.
> * value.h (make_cv_value): Declare.
>
> gdb/doc/ChangeLog:
>
> 2015-04-27 Siva Chandra Reddy <sivachandra@google.com>
>
> * python.texi (Values From Inferior): Add descriptions of new
> methods gdb.Value.reference_value and gdb.Value.const_value.
>
> gdb/testsuite/ChangeLog:
>
> 2015-04-27 Siva Chandra Reddy <sivachandra@google.com>
>
> * gdb.python/py-xmethods.cc: Enhance test case.
> * gdb.python/py-xmethods.exp: New tests.
> * gdb.python/py-xmethods.py (A_indexoper): New xmethod worker
> function.
> (B_indexoper): Likewise.
> (global_dm_list) : Add new xmethod worker functions.
next prev parent reply other threads:[~2015-05-04 23:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 13:30 Siva Chandra
2015-04-27 14:54 ` Eli Zaretskii
2015-05-04 23:40 ` Siva Chandra [this message]
2015-05-07 23:30 Doug Evans
2015-05-10 0:36 ` Siva Chandra
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=CAGyQ6gxxeAt14dpyyhxYid3FOWOwrumrKvd7FEmpxYoBrE51ug@mail.gmail.com \
--to=sivachandra@google.com \
--cc=dje@google.com \
--cc=gdb-patches@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).